Check whether changed source files have corresponding test files. Use for code quality review before merging a PR, or when asked whether new code has tests.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Check whether changed source files have test coverage.
!git diff --name-only HEAD~1 2>/dev/null || git diff --name-only origin/main...HEAD 2>/dev/null || echo "none"
Filter the list above to source files only. Exclude:
test/, spec/, __tests__/, tests/).test., .spec. in the name.md, .json, .yaml, .yml, .lock, .txt, .env, .gitignore*.config.ts, *.config.js, vite.config.*, jest.config.*If the output was "none" or after filtering there are no source files, output: COVERAGE FINDINGS: none — no changed source files detected
For each changed source file, derive candidate test file paths using these conventions:
Given source file src/utils/parser.ts, check for:
src/utils/parser.test.tssrc/utils/parser.spec.tssrc/utils/__tests__/parser.tssrc/utils/__tests__/parser.test.tstests/utils/parser.test.tstests/utils/parser.spec.tstest/utils/parser.test.tstest/utils/parser.spec.tsApply the same pattern for .py, .js, .jsx, .tsx, .go, .rb files, substituting the appropriate test file extension:
_test.py or test_<name>.py.test.js, .spec.js, .test.ts, .spec.ts_test.go in the same directory_spec.rb in spec/Use Glob to check whether any of the candidate paths exist.
If a test file is found, use Grep to check whether it imports or requires the source file, or references the source file's name. If no import is found, mark as "test file exists but may not cover new changes".
Output exactly:
COVERAGE FINDINGS:
- <source-file> — no test file found
- <source-file> — test file exists but may not cover new changes
Examples:
COVERAGE FINDINGS:
- src/auth/loginHandler.ts — no test file found
- src/utils/formatDate.ts — test file exists but may not cover new changes
If all changed source files have test files that reference them: output exactly COVERAGE FINDINGS: none
Do not add any prose before or after the findings block.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Write an Architecture Decision Record (ADR) document for a technical decision. Use when documenting a technical choice, architectural decision, or design decision.
The English summary is being prepared. Showing the original description.
REST API design conventions for this codebase. Use when writing or reviewing API endpoints, route definitions, response formatting, or client code that calls the API.
The English summary is being prepared. Showing the original description.
Automatically format code files after every edit using Prettier and ESLint. Active in the background whenever Claude edits a file. Formatting is silent — no prompts, no output unless a formatter fails. Use when you want consistent formatting enforced automatically during a coding session.
The English summary is being prepared. Showing the original description.
Create a git branch named after a GitHub issue.
The English summary is being prepared. Showing the original description.
Draft the changelog entry for all unreleased commits in Keep a Changelog format. Groups commits into Added, Changed, Fixed, Removed, and Security. Use before releasing a new version or when updating CHANGELOG.md.
The English summary is being prepared. Showing the original description.
Draft a CHANGELOG.md entry for the current changes in Keep a Changelog format. Use when releasing, tagging a version, or updating CHANGELOG.md.
The English summary is being prepared. Showing the original description.