requesting-code-review

Automated code review uses a specialized subagent to evaluate git changes against defined requirements, catching architectural issues and testing gaps before merging. You provide the base commit hash and implementation details to trigger the structured review process.

A subagent-based code review dispatches a specialized reviewer to analyze your git diff independently, ensuring consistent feedback without polluting your active development session context. It evaluates changes against structured templates for quality assurance and production readiness.

Requirement verification checks implemented features against the established plan or requirements document using a code-reviewer subagent. This ensures strict adherence to specifications and catches missing edge cases or architectural deviations in the git diff.

Automated code review integrates with existing git workflows by using commit hashes to define the review scope. It requires git integration to establish the base commit and a structured template to ensure consistent feedback across development tasks.

Catching architectural issues in a git diff is best handled by dispatching a specialized subagent to perform a structured review against production readiness checks. This isolates the analysis from your active session and ensures rigorous quality assurance.

A structured template is required for automated code reviews to ensure consistent feedback across all development tasks. The template guides the subagent's evaluation of code changes against defined requirements and architectural validation standards.