commit.review

You can run an automated preflight code review by staging your changes and triggering a sub-agent to analyze the git diff of HEAD, producing a structured report of issues and suggested fixes.

The best way to check for DRY violations and missing tests is to use a sub-agent-assisted review that reads code review standards and analyzes staged files to highlight duplication, naming clarity problems, and test coverage gaps.

Yes, this preflight code review integrates directly with Git-based workflows, requiring access to the git diff of HEAD and staged changes to perform thorough quality assurance before you run tests.

Yes, you can identify naming clarity problems and anti-patterns by spawning a sub-agent to inspect changed files, which evaluates the code against quality standards and reports maintainability concerns.

A sub-agent based code review structures its feedback by producing a report that details the file, the specific issue, its severity level, and suggested fixes for each identified quality problem.

This pre-test code quality review focuses strictly on identifying quality issues, DRY violations, and missing tests in changed files, meaning it serves as an early assessment rather than executing or validating the tests themselves.