What problem does it solve? After making code changes, developers often skip local verification or forget to add tests for new logic, letting defects slip through to CI or production. This Skill defines which checks to run for each change surface and how to judge whether new tests are required. ## Core Features & Use Cases - Full check matrix: Maps backend changes to pytest, ruff, and pyright, and frontend changes to vitest, eslint, and tsc --noEmit. - Scoped test execution: Runs only the pytest scope you touched locally, leaving the full suite, e2e, and coverage gates to CI to avoid saturating the shared dev host. - Test-necessity judgment: Provides explicit criteria for when to add tests — new branches, bug fixes, interface signature changes, and dead code deletion. - Use Case: After fixing a bug in a Python API endpoint, run pytest for the touched module plus ruff and pyright, then add a regression test so the same bug cannot reappear. ## Quick Start After finishing my code changes, run the appropriate lint, type check, and test commands for the files I touched and tell me whether new tests are needed.
