requesting-code-review

Automated code review dispatches specialized subagents to evaluate git diffs against project requirements, identifying architectural and security issues before merge. It requires specific git commit SHAs and structured plan documentation to generate actionable, context-aware feedback.

A subagent evaluates code changes by comparing precise git diffs provided as commit SHAs against structured plan documentation. This context-aware mechanism ensures the reviewer focuses on functional, architectural, and security compliance before finalizing the merge.

To start systematic code quality assurance, you need the base and head git commit SHAs representing your changes, alongside structured plan documentation. This inputs allows the reviewer agent to verify code meets original design and performance standards.

Yes, structured code review prevents architectural drift by enforcing an objective evaluation process before changes merge into the main codebase. It verifies implementations against original design plans to ensure ongoing architectural integrity and security.

You need to provide git commit SHAs when you want to trigger a code review subagent for a specific set of changes. The SHAs define the exact diff boundaries for the reviewer to analyze against your project requirements.

No, structured plan documentation is required alongside git commit SHAs. The reviewer agent relies on this plan to understand the original design requirements and generate focused, actionable feedback regarding functional and security issues.