requesting-code-review

Automated code review before merging uses a subagent to validate implementation quality based on completed task artifacts. It generates focused review briefs mapping to the work done, ensuring changes are evaluated against the plan before integration into the main branch.

Subagent-driven code review orchestrates a dedicated evaluation agent to assess changes, risks, and quality. It references git SHAs and artifacts to support a precise, repeatable review process that validates whether implementation meets the original plan.

Start a code review by dispatching the code-reviewer subagent after completing a task. Summarize what was implemented and what feedback is requested to automatically generate focused briefs mapping to the completed work.

Automated code review applies to both individual contributors and teams in task-driven development. It supports feature implementations and pre-merge validation, ensuring changes are evaluated regardless of team size.

The code review process references git SHAs and artifacts to support precise, repeatable review workflows. This traceable approach ensures feedback is artifact-driven and explicitly validates the implementation against the original plan.

Validating implementation quality in task-driven development is best handled by a structured code-review protocol that applies explicit plan-based validation. It uses a subagent to assess risks and generate artifact-driven feedback before merging.