quality-gate

Pre-computed context

Current branch: !git branch --show-current 2>/dev/null || echo "unknown" Working tree status (empty = clean): !{ git status --porcelain 2>/dev/null || echo "(git status unavailable)"; } | head -20 Open PRs (match headRefName to current branch above; baseRefName is the PR's real base): !gh pr list --json number,title,headRefName,baseRefName --limit 10 2>/dev/null || echo "unknown"

Purpose

Review is the quality checkpoint between "code works" and "code is ready." This skill structures that step so changes are inspected for consistency, correctness, and alignment with the project's conventions before verification or PR creation. Self-review catches errors tests miss. Inconsistencies, loose ends, convention drift, design shortcuts. Delegated reviews (code, architecture, security) bring specialized scrutiny the implementer's tunnel vision would miss.

Depth, not breadth. This skill picks ONE lens per invocation. For a multi-surface fan-out that runs many reviewers at once and ranks their combined findings, use this plugin's fanout skill instead.

Shared inputs

• Review diff base. mode-scoped override first: close-out does not use this base at all. A spec container is not a branch, so that mode derives a container-scoped basis of its own, per execution shape (context/close-out.md "Why it needs its own diff basis"). Every other mode uses the base below. When an open PR exists for the branch, its baseRefName is the base: dispatched reviewers diff git merge-base origin/<baseRefName> HEAD. The pre-computed PR list above is capped; when the current branch is absent from it, run gh pr list --head <current-branch> --json number,baseRefName before concluding no PR exists. Otherwise git merge-base origin/HEAD HEAD (falling back to the remote's resolved default branch via git ls-remote --symref, then origin/main, then HEAD) so committed-clean branches still show their changes; untracked files come from git ls-files --others --exclude-standard.
• Severity vocabulary, the project's own review docs when present; else ${CLAUDE_PLUGIN_ROOT}/context/severity.md.
• Criteria resolution. Review criteria resolve through the standards index per the plugin binding ${CLAUDE_PLUGIN_ROOT}/reference/standards-contract.md (its "Resolution ladder" section owns the procedure), detailed in context/criteria.md.
• Findings location. Resolve through the plugin binding, ${CLAUDE_PLUGIN_ROOT}/reference/topic-docs.md, which owns the resolution ladder, its non-interactive collapse, the <branch-slug> and <UTC-timestamp> spec, and the self-ignore guard. Resolve the home; never assume its shape, the ladder's rungs do not all compose a reviews/<branch-slug> segment. Durable findings are <UTC-timestamp>-<mode>.md in the resolved directory. Write repo-relative paths only, never absolute machine paths.