requesting-code-review

Automated code review before merging is handled by dispatching a code-reviewer subagent to evaluate recent changes. The skill enforces a structured feedback template and requires fixes before proceeding to merge.

Structured code review feedback for new features is delivered through a templated flow that categorizes issues into critical, important, and minor. This standardizes evaluation quality and clarifies what needs immediate attention.

Code review should be requested after each task, after completing a major feature, and before merging to main. This ensures timely feedback and catches issues before they cascade into larger problems.

The code review process enforces workflow guardrails by requiring feedback to be acted upon before proceeding. This ensures all identified critical, important, and minor issues are resolved before merging.

A subagent can be dispatched with precisely crafted context to automatically review recent git changes. It evaluates the work and returns a structured verdict to guide necessary corrections.

Automated code review catches issues early and standardizes feedback to prevent high-quality code degradation. It guarantees timely, consistent evaluations after tasks and before merges, complementing manual checks.