requesting-code-review

To automate code review for git diffs, you can dispatch a specialized subagent to evaluate specific commit ranges against your defined requirements, identifying critical bugs and architectural deviations. This ensures production readiness through structured feedback loops.

The best way to check code quality without consuming primary session context is offloading the evaluation to a specialized subagent. This subagent analyzes the provided git diff ranges and requirements independently, preventing the leakage of irrelevant session history into the review process.

Yes, you can use a subagent to verify code changes against architectural standards. By providing the subagent with precise git ranges and predefined technical requirements, it evaluates the diff to catch architectural flaws and missing edge cases before merging.

To review a specific commit range for testing gaps and bugs, provide the base commit, current head, and implementation description to a reviewer subagent. It evaluates the targeted changes to identify critical bugs, architectural deviations, and missing test coverage.

Yes, automated code review works with specific git commit ranges. You provide the exact base commit and head to the subagent, ensuring the analysis stays context-aware and focused only on the changes relevant to the implementation plan.

You should not use a subagent for code quality assessment when you lack defined technical requirements or precise git commit ranges. The subagent relies on these predefined standards and specific ranges to provide rigorous analysis and structured feedback.