requesting-code-review

You can automate code review by dispatching a code-reviewer subagent to evaluate your changes. This routes your work product to a dedicated reviewer for early, structured feedback before issues cascade.

A subagent workflow for code review dispatches a dedicated reviewer with precisely crafted context. This mechanism evaluates the work product independently, keeping the reviewer focused on requirements rather than your session's thought process.

Code review automation preserves your session context by sending only crafted context to the reviewer subagent, never your session history. This keeps the reviewer focused on the work product while retaining your context for continued work.

Yes, you can use a code reviewer subagent for pre-merge checks. The reviewer provides contextual evaluation of your work product against requirements, integrating flexibly across feature work and pre-merge verification.

You need to dispatch a code review subagent after completing a task to catch issues early. This provides structured feedback focused on your work product, preventing potential problems from cascading into larger issues.

The best way to get focused feedback is dispatching a code reviewer subagent with precisely crafted context. This approach evaluates the work product against requirements without exposing your session's thought process.