present-local

Local-Mode Code Review Presenter

This skill is the canonical presenter for /code-review local mode at stage_29_present. It is split out of commands/start.md so the orchestration spine stays lean; the orchestrator invokes it when MODE=local and stage_29_present is reached.

Gate A hygiene-only early-exit is not in this skill. That path is mode-agnostic (fires for both MODE=local and MODE=github) and the hygiene presentation lives in start.md adjacent to the Gate A definition — the orchestrator handles it inline, not via this skill.

---

Local Mode: Present Results (stage_29_present, MODE=local)

Mark "Present findings by severity" in_progress.

Render the report below. Three text conventions run through this template, so it stays clear which lines you emit verbatim and which are directions to you:

• ## section headers (Repo Hygiene, BLOCKING, …) are the report's own structure — emit them as written, with the live [count] substituted.
• Fenced code blocks are card/footer templates — instantiate one per finding (or per stat block), substituting the {PLACEHOLDER} and [bracketed] fields.
• [bracketed] and {BRACED} tokens are instructions or substitution points, never literal output.

Output in this format:

# Code Review Results

**Scope:** [staged/branch/files]
**Files Reviewed:** [count]

Reviewer Fleet block (PLN-725 Phase 9 / v2.23.0). Do NOT write the Reviewers / Model Routing / Fleet lines from scratch. Run the canonical renderer and embed its output verbatim:

python <HELPERS> render-fleet-summary --cr-dir <CR_DIR>

The renderer consumes <CR_DIR>/spawn.json (sections: spec — intended fleet from stage_19b; verification — runtime tally from stage_20b; route — model assignments from Gate B). The output is a deterministic markdown block of 2–9 lines — 2–4 for the core Reviewers / Model Routing / Fleet section, plus up to 5 conditional note bullets — covering:

• Reviewers — the actual fleet that spawned (with the rule-resolved vs LLM-proposed split surfaced on domain critics so the operator can tell operator-configured coverage apart from one-off LLM proposals).
• Model Routing — the per-agent model assignments derived from spawn.json.route.
• Fleet — N intended | N ran | N required missing so the operator sees the runtime tally without scrolling to Verifier Stats.
• Notes (conditional) — only emitted when the run was non-default: BLOCKING-sanitized arbitration, missing required reviewers (runtime crash), BHA partitions capped by post-arbitrate budget, PLN-723 deferral, malformed-plan required skips. Each note is a single bullet so the section stays scannable; multiple notes can fire together.