requesting-code-review

Automating a code review before merging involves dispatching a subagent with the Base and Head SHAs to evaluate code quality, architecture, and production readiness. It applies a structured review template to verify alignment with requirements and surface actionable issues.

Subagent-driven development dispatches automated reviewers to catch issues early after completing tasks. You need it to enforce pre-merge quality assurance, validate changes against explicit plans, and prevent cascading defects in your workflow.

Dispatch the code-reviewer subagent by providing the required BASE_SHA and HEAD_SHA inputs after major feature completion. The subagent initiates a structured review to assess testing, architecture, and production readiness before proceeding.

Yes, the code review workflow strictly enforces BASE_SHA and HEAD_SHA inputs to identify changes between commits. These inputs allow the subagent to evaluate code quality, architecture, and verify alignment with your requirements.

The best way to catch code quality issues early is dispatching a code-reviewer subagent after each task. This automates quality assurance checks against a structured template to surface actionable issues and facilitate safer merges to main.

Validating code changes against explicit plans is achieved by dispatching the code-reviewer subagent with your commit SHAs. The subagent uses a structured review template to verify alignment with requirements, assess architecture, and determine production readiness.