requesting-code-review

To run a pre-merge code review, collect your BASE_SHA and HEAD_SHA using git rev-parse, then dispatch a general-purpose code reviewer to analyze the diff and triage issues by severity before proceeding.

Subagent-driven development catches architectural issues by dispatching a targeted code review after each completed subagent task, evaluating the precise git diff range to identify bugs and requirement mismatches early.

Yes, you can use this code review skill for ad-hoc checks during risky refactors by collecting the relevant git SHAs and dispatching a reviewer to analyze the changes before you continue.

The code reviewer triages diff analysis feedback by labeling issues as Critical, Important, or Minor, recommending specific next actions and requiring Critical and Important fixes before you proceed.

Yes, you need to manually specify the git SHA range for a pull request review by collecting the BASE_SHA and HEAD_SHA values with git rev-parse to ensure the reviewer evaluates only the intended changes.

You should not use an automated pre-merge code review when you are blocked on unresolved Critical or Important feedback, as the workflow requires acting on these severity levels before moving forward.