requesting-code-review

To request a code review, fill in a structured template detailing what was implemented, the plan or requirements, and the git SHAs. This standardizes the review process and provides clear context for reviewers before merging.

A code review request template should include placeholders for what was implemented, the plan or requirements, and the specific git SHAs. This ensures reviewers have the necessary context to catch issues early and prevent cascading defects.

You need a formal code review checkpoint in task-based development workflows where features are built incrementally. It acts as a mandatory or optional trigger to catch issues early before merging.

You can automate the code review feedback flow by dispatching a code-reviewer subagent after filling out the review request template. This seamlessly integrates automated feedback into your quality assurance workflow before merging.

Yes, the code review process is designed for standard git workflows. It standardizes review requests by utilizing git SHAs to guide reviewers through task-based development before pulling or merging branches.