comprehensive-review

Run git diff to list changed files, then evaluate the code against the 7 criteria: blindspots, clarity, maintainability, security, performance, documentation, and style. Document all findings, fix or defer each one with a tracking issue, and post the review artifact to the GitHub issue.

The criteria are blindspots, clarity/consistency, maintainability, security risks, performance implications, documentation, and standards/style. Each criterion includes a checklist of concrete questions such as edge-case handling, N+1 queries, and input validation.

PR creation is blocked by a PreToolUse hook and review-gate until a review artifact is posted to the GitHub issue in the exact required format. The artifact must show "Unaddressed: 0" and "Review Status: COMPLETE".

A security review is mandatory whenever changed files match security-sensitive patterns such as auth, middleware, api, password, token, or secret. In that case the security-review skill or security-reviewer subagent must be invoked and the artifact marked "Security-Sensitive: YES".

Yes, but only by creating a tracking issue for each deferred finding and linking it in the review artifact. Deferring without a tracking issue is not permitted, and the unaddressed count must remain zero.