requesting-code-review

To automate code review for git changes, the skill dispatches a specialized code-reviewer subagent to analyze specific git diffs against requirements, returning structured feedback categorized by severity before you merge to main.

Subagent-driven code quality assurance works by passing specific git SHAs and change descriptions to a code-reviewer subagent, which performs contextual analysis without the entire session history to verify implementation correctness and production readiness.

Yes, you can get structured feedback on code diffs without full session context by providing the code-reviewer subagent with specific git SHAs and a description of the changes, ensuring a focused and relevant quality assessment.

The best way to verify implementation requirements and catch bugs is to dispatch a code-reviewer subagent that categorizes issues into Critical, Important, and Minor severities, providing actionable recommendations for production readiness.

Yes, you need specific git commit SHAs to start the code review workflow, as the process involves obtaining these identifiers to pass precise code diffs and requirements to the code-reviewer subagent for contextual analysis.