requesting-code-review

To automate code review checks before merging, dispatch a dedicated code-reviewer subagent to verify implementations against documented plans. This ensures plan alignment, quality standards, and production-readiness are evaluated before changes reach main.

You should trigger a code-reviewer subagent after each subagent-driven task, after completing major features, or before merging to main. Optional use is recommended when stuck or during refactoring to prevent cascading issues.

The best way to verify implementations against documented requirements is dispatching a code-reviewer subagent. It compares changes against the documented plan and provides structured feedback via a markdown template.

No, this automated code review workflow requires no external dependencies. It operates entirely within your environment by dispatching the code-reviewer subagent using the provided markdown template.

A code-reviewer subagent surfaces feedback and decisions by documenting them through a structured code-reviewer.md template. This workflow ensures early feedback is captured before moving forward with the implementation.

Yes, you can use this code review approach when stuck or refactoring existing code. While primarily applied after tasks or before merging to main, optional use during these scenarios helps catch issues early.