guild-request-review

To run a fresh-context code review before merging, dispatch a subagent using the code-reviewer.md template, providing the implementation summary, plan, and git base and head SHAs to verify production readiness.

A fresh-context code review is an independent assessment of code changes performed by a subagent that evaluates the work product against requirements, rather than relying on the session history of the original implementation.

You should use a pre-merge code review subagent after completing each individual task, after finishing major features, and before merging to main, ensuring you catch issues early and maintain alignment with requirements.

You need to provide the implementation summary, the original plan or requirements, the base SHA, the head SHA, and a description, filling in the placeholders in the code-reviewer.md template to receive a structured assessment.

The code-reviewer subagent returns a structured assessment of your code changes that includes identified strengths, issues categorized by severity, and actionable recommendations to guide fixes and risk management.

Yes, a fresh-context code review works without external dependencies, as it operates by dispatching a subagent internally to evaluate the provided git SHAs and implementation details against the plan.