Files
nuzlocke-tracker/CLAUDE.md
Julian Tabel 3a64661760
Some checks failed
CI / backend-lint (push) Failing after 1m4s
CI / actions-lint (push) Failing after 6s
CI / frontend-lint (push) Successful in 59s
Align repo config with global development standards
- Add missing tsconfig strictness flags (noUncheckedIndexedAccess,
  exactOptionalPropertyTypes, noImplicitOverride,
  noPropertyAccessFromIndexSignature) and fix all resulting type errors
- Replace ESLint/Prettier with oxlint 1.48.0 and oxfmt 0.33.0
- Pin all frontend and backend dependencies to exact versions
- Pin GitHub Actions to SHA hashes with persist-credentials: false
- Fix CI Python version mismatch (3.12 -> 3.14) and ruff target-version
- Add vitest 4.0.18 with jsdom environment for frontend testing
- Add ty 0.0.17 for Python type checking (non-blocking in CI)
- Add actionlint and zizmor CI job for workflow linting and security audit
- Add Dependabot config for npm, pip, and github-actions
- Update CLAUDE.md and pre-commit hooks to reflect new tooling
- Ignore Claude Code sandbox artifacts in gitignore

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-16 20:39:41 +01:00

1.4 KiB

Branching Strategy

  • Never commit directly to main. main is always production-ready.
  • Day-to-day work happens on develop.
  • New work is done on feature/* branches off develop.
  • Merge flow: feature/*developmain.
  • Squash merge feature/* into develop (one clean commit per feature).
  • Merge commit develop into main (marks deploy points).
  • Always git pull the target branch before merging into it.

Pre-commit Hooks

This project uses pre-commit to run linting and formatting checks before each commit.

Setup: pip install pre-commit && pre-commit install

Hooks configured:

  • Backend: ruff check --fix and ruff format on Python files under backend/
  • Frontend: oxlint, oxfmt --check, and tsc -b on files under frontend/

Frontend hooks require npm ci in frontend/ first (they use npx to run from local node_modules).

Instructions

  • After completing a task, always ask the user if they'd like to commit the changes.
  • Before working on a bean, always set it to in-progress. After the changes related to the bean are committed, mark it as completed.
  • If a bean is marked as draft, refine it first before starting work on it.
  • When completing a bean that has a parent (epic, feature, etc.), check the parent's checklist/success criteria for items that can now be marked as completed and update them.