requesting-code-review

To automate code review for specific Git commits, dispatch an AI reviewer agent to analyze isolated commit ranges against defined project requirements. This process evaluates architecture, quality, and logic to catch bugs before merging changes.

The best way to catch architectural flaws before merging is to use an agent-driven review process that compares your feature branch against the main branch. This ensures new code aligns with the original technical plan and meets production standards.

Yes, you can dispatch a dedicated AI reviewer to verify if new code aligns with an implementation plan. The reviewer uses a structured template to assess architecture, quality, and requirements adherence within your specified Git SHA ranges.

Agent-driven code analysis works with Git history by leveraging Git SHA ranges to provide the reviewer with precise, isolated diffs. This allows the AI agent to perform comparative code analysis and identify critical bugs accurately.

Yes, you need general-purpose task tools to perform systematic code quality assurance. The review process requires access to Git history and the ability to execute these tools for accurate comparative code analysis.

You should avoid using an automated code review agent for changes outside a defined Git commit range or when project requirements are undefined, as the analysis relies on comparing specific diffs against established technical plans.