Add pre-commit to run standard hooks plus codespell

.gitattributes

@@ -1,2 +1,2 @@
 * text=auto eol=lf
-dist/** -diff linguist-generated=true
+dist/** -diff linguist-generated=true

.github/CODEOWNERS

@@ -1 +1 @@
-* @dhavalgojiya
+* @dhavalgojiya

.github/workflows/ci-test.yml

@@ -7,8 +7,18 @@ on:
     branches: [ "main" ]
 
 jobs:
+  # -----------------
+  # Job 1: Pre-commit
+  # -----------------
+  pre-commit:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v6
+      - uses: pre-commit/[email protected]
+      - uses: pre-commit-ci/[email protected]
+        if: always()
   # -----------------------------
-  # Job 1: Package Checks & Build
+  # Job 2: Package Checks & Build
   # -----------------------------
   package:
     runs-on: ubuntu-latest
@@ -90,7 +100,7 @@ jobs:
         run: |
           echo "Pinging Solr Core: ${SOLR_CORE}"
           RESPONSE=$(curl -s --fail "http://127.0.0.1:8983/solr/${SOLR_CORE}/admin/ping?wt=json")
-          
+
           if echo "$RESPONSE" | grep -q '"status":"OK"'; then
             echo "🎉 Solr is healthy and responding"
           else

.gitignore

@@ -112,4 +112,4 @@ out
 .yarn/unplugged
 .yarn/build-state.yml
 .yarn/install-state.gz
-.pnp.*
+.pnp.*

.pre-commit-config.yaml

@@ -0,0 +1,48 @@
+# Learn more about this config here: https://pre-commit.com/
+
+# To enable these pre-commit hooks run:
+# `pipx install pre-commit` or `brew install pre-commit`
+# Then in the project root directory run `pre-commit install`
+
+exclude: dist/
+
+repos:
+  - repo: https://github.com/pre-commit/pre-commit-hooks
+    rev: v6.0.0
+    hooks:
+      - id: check-added-large-files
+      - id: check-case-conflict
+      - id: check-docstring-first
+      - id: check-executables-have-shebangs
+      - id: check-illegal-windows-names
+      - id: check-json
+      - id: check-merge-conflict
+      - id: check-shebang-scripts-are-executable
+      - id: check-symlinks
+      - id: check-toml
+      - id: check-vcs-permalinks
+      - id: check-xml
+      - id: check-yaml
+      - id: destroyed-symlinks
+      - id: detect-aws-credentials
+        args:
+          - --allow-missing-credentials
+      - id: detect-private-key
+      - id: end-of-file-fixer
+      - id: file-contents-sorter
+      - id: forbid-new-submodules
+      - id: forbid-submodules
+      - id: mixed-line-ending
+        args:
+          - --fix=lf
+      - id: sort-simple-yaml
+      - id: trailing-whitespace
+
+  - repo: https://github.com/codespell-project/codespell
+    rev: v2.4.1
+    hooks:
+      - id: codespell
+        args:
+          - --ignore-words-list=nd
+        additional_dependencies:
+          - tomli

CODE_OF_CONDUCT.md

@@ -51,17 +51,17 @@ Community Moderators take reports of violations seriously and will make every ef
 
 If an investigation by the Community Moderators finds that this Code of Conduct has been violated, the following enforcement ladder may be used to determine how best to repair harm, based on the incident’s impact on the individuals involved and the community as a whole. Depending on the severity of a violation, lower rungs on the ladder may be skipped.
 
-1. **Warning**  
-   Event: A violation involving a single incident or series of actions.  
+1. **Warning**
+   Event: A violation involving a single incident or series of actions.
    Consequence: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
 
-2. **Temporary Ban**  
-   Event: A violation involving a series of actions or a single serious incident.  
+2. **Temporary Ban**
+   Event: A violation involving a series of actions or a single serious incident.
    Consequence: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
 
-3. **Permanent Ban**  
-   Event: A pattern of repeated code of conduct violations that other steps on the ladder have failed to resolve, or a violation so serious that the Community Moderators determine there is no way to keep the community safe with this person as a member.  
-   Consequence: Access to all community spaces, tools, and communication channels is removed. In general, permanent bans should be rarely used, should have strong reasoning behind them, and should only be resorted to if working through other remedies has failed to change the behavior.  
+3. **Permanent Ban**
+   Event: A pattern of repeated code of conduct violations that other steps on the ladder have failed to resolve, or a violation so serious that the Community Moderators determine there is no way to keep the community safe with this person as a member.
+   Consequence: Access to all community spaces, tools, and communication channels is removed. In general, permanent bans should be rarely used, should have strong reasoning behind them, and should only be resorted to if working through other remedies has failed to change the behavior.
    Repair: There is no possible repair in cases of this severity.
 
 This enforcement ladder is intended as a guideline. It does not limit the ability of Community Managers to use their discretion and judgment, in keeping with the best interests of our community.

LICENSE

@@ -18,4 +18,4 @@ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
 AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
 LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
 OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
+SOFTWARE.

README.md

@@ -4,7 +4,7 @@
   <img src="https://raw.githubusercontent.com/DhavalGojiya/setup-solr-action/main/assets/images/project-logo.png" width="90%" alt="Project Apache Solr Logo"/>
 </p>
 
-Easily spin up an [Apache Solr](https://solr.apache.org/) instance inside your **GitHub Actions CI** pipeline.  
+Easily spin up an [Apache Solr](https://solr.apache.org/) instance inside your **GitHub Actions CI** pipeline.
 This action makes it simple to provision Solr during your tests or builds, without needing complex manual setup.
 
 It will:
@@ -223,14 +223,14 @@ This will simulate your workflow on your local machine using [act](https://githu
 
 ## 🤝 Contributing
 
-Want to improve this project? Contributions are welcome!  
+Want to improve this project? Contributions are welcome!
 Please check out the [Contributing Guide](./CONTRIBUTING.md) for details.
 
 ---
 
 ## 👨‍💻 About the Author
 
-Hi, I’m **Dhaval Gojiya** — a passionate **Software Engineer** and also a **Farmer** 🌱.  
+Hi, I’m **Dhaval Gojiya** — a passionate **Software Engineer** and also a **Farmer** 🌱.
 I love building open-source tools that simplify workflows, while staying curious and grounded in both tech and nature.
 
 ---

package.json

@@ -27,4 +27,4 @@
     "tsup": "^8.5.0",
     "typescript": "^5.9.2"
   }
-}
+}