fanout

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" Committed diff size vs default-base merge base (recompute against the PR's baseRefName when it differs): !bash "${CLAUDE_PLUGIN_ROOT}/skills/fanout/scripts/diff-vs-base.sh" 2>/dev/null || echo "unavailable" Uncommitted diff size: !git diff --shortstat HEAD 2>/dev/null || echo "unavailable"

Purpose

Breadth review. Where this plugin's quality-gate skill picks ONE lens per invocation, this skill fans out across MANY finding-producing surfaces at once, then normalizes their incomparable outputs into one severity-ranked report persisted to disk.

The hard problem this skill owns: the surfaces emit heterogeneous free-text on two independent axes (severity, confidence), and most populate only one. A 5-stage normalization pipeline (extraction → severity crosswalk → confidence enum → dedup → agreement/rank) is therefore unavoidable. context/findings-normalization.md.

Review modes report; a separate fix action applies. The default and run-everything modes fan out, normalize, and persist findings, mutating nothing but the findings file. The fix action consumes the persisted findings and is the only mode that touches the working tree.

Shared inputs

• Review diff base, when an open PR exists for the branch, its baseRefName is the base: dispatched surfaces 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). Never a hardcoded git diff HEAD, which is empty on a clean committed branch.
• Severity vocabulary, the project's own review docs when present; else ${CLAUDE_PLUGIN_ROOT}/context/severity.md.
• Findings location. Resolve through the plugin binding, ${CLAUDE_PLUGIN_ROOT}/reference/topic-docs.md, which owns the resolution ladder, the <branch-slug> and timestamp spec, the non-interactive collapse, 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, and the review modes' writer and the fix action's reader must land in the same directory or findings go silently unseen. Read the binding rather than working from the default's shape.