feat: precommit checks updated: added ESLint and Svelte checks for frontend

[HardMax71]

---

Summary by cubic

Adds ESLint and Svelte Check as pre-commit hooks for the frontend to catch issues before commits, aligned with CI. Also removes the ESLint --ext flag to match CI and avoid mismatched linting.

• New Features

  • Adds eslint and svelte-check hooks for frontend/src (.ts, .svelte), using the same commands as CI.
  • Updates CONTRIBUTING.md to list the new checks.

• Bug Fixes

  • Removes unnecessary --ext from the ESLint hook to align with CI.

^{Written for commit 119e086. Summary will update on new commits.}

Summary by CodeRabbit

• Chores

  • Added frontend pre-commit hooks to run linting and type-checking for frontend files to enforce code quality during development.

• Documentation

  • Updated contribution guidelines to document the new frontend pre-commit quality checks.

[coderabbitai]

📝 Walkthrough

Walkthrough

Adds two frontend pre-commit hooks (eslint and svelte-check) to .pre-commit-config.yaml and updates CONTRIBUTING.md to document these hooks for TypeScript and Svelte files under frontend/src/.

Changes

Cohort / File(s)	Summary
Frontend pre-commit config & docs \.pre-commit-config.yaml, CONTRIBUTING.md	Added eslint-frontend and svelte-check-frontend hooks targeting `frontend/src/.*.(ts

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• chore: precommit checks + added missing docs #88: Added backend pre-commit hooks (ruff and mypy); closely related configuration changes for local pre-commit setup.

Poem

🐰
Hop, I found a lint and a check,
Svelte and TS now shipwrecks… less!
Pre-commit hops in, neat and spry,
Catching bugs before they fly. 🐇✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and specifically summarizes the main change: adding ESLint and Svelte checks to pre-commit configuration for frontend code quality.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/precommit

---

No actionable comments were generated in the recent review. 🎉

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[cubic-dev-ai]

No issues found across 2 files

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In @.pre-commit-config.yaml:
- Around line 25-31: The ESLint pre-commit hook (id: eslint-frontend) is passing
the now-unsupported CLI flag `--ext .ts,.svelte` in the entry command; remove
that flag so the entry reads the flat-config-managed patterns (i.e., change the
entry string from "bash -c 'cd frontend && npx eslint src --ext .ts,.svelte'" to
simply run ESLint via "bash -c 'cd frontend && npx eslint src'"), relying on the
existing pre-commit `files` pattern and the flat config in
frontend/eslint.config.js to determine targets.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud