requesting-code-review

Standardize code review requests by using structured templates with placeholders for implemented features, requirements, base and head SHAs, and descriptions to ensure clear feedback. This aligns peer reviews with project goals during development cycles.

Trigger code review requests after completing individual tasks, before merging major feature implementations, or during refactoring phases. Timely requests prevent late reviews, confusing feedback, and merged defects across git workflows.

The best way to structure pre-merge code review feedback is by filling out a standardized template detailing what was implemented, the plan, and the git SHAs. This ensures reviews happen predictably with documented rationale.

Structured code review planning integrates with subagent-driven development by providing templates and workflow milestones that trigger reviews predictably. It uses documented rationale and specific git SHAs to maintain consistency across development cycles.

Inconsistent code reviews lead to merged defects because feedback happens late or without standardized templates, causing misaligned project goals and missing critical issues. Structured milestones ensure timely, clear review requests.

Yes, you can use this code review template for refactoring checks in git workflows. It provides structured placeholders for base and head SHAs, descriptions, and plans to speed up feedback and standardize quality checks.