requesting-code-review

Automating code reviews before merging involves dispatching a specialized subagent with precise context, such as code diffs and requirements, to isolate the review from broader session history. This ensures changes are thoroughly vetted for production readiness without manual intervention.

A subagent dispatch for pre-merge verification is an automated process that sends a specialized code reviewer precise code diffs and requirements. This isolates the analysis from session history to identify potential bugs or architectural flaws before merging.

To structure feedback for a code review, categorize identified issues by severity, such as Critical, Important, or Minor, and provide actionable recommendations. This structured feedback ensures changes adhere to requirements and are production-ready.

Yes, you need git to request an automated code review because the process requires git commands to establish commit SHAs. These SHAs are necessary to generate the precise code diffs for the subagent's structured markdown template input.

A code reviewer subagent analyzes changes against a design document by receiving precise code diffs and requirements as input. This contextual review isolates the analysis, categorizing issues by severity to identify potential bugs or architectural flaws.

Yes, you can isolate code review context from broader session history by dispatching a specialized subagent with precise code diffs and requirements. This ensures the reviewer analyzes only the specific changes against the design document.