reviewer-baselinelisted

# Reviewer Baseline Protocol This skill defines the shared review protocol that ALL code reviewer agents follow. It ensures consistent confidence scoring, finding classification, and output format across the review system. > **Per-reviewer repo extension (load second).** If `.claude/second-shift/review-context/<your-agent-name>.md` exists in the repo under review, load it after the shared `review-context.md` — it carries this reviewer's repo-specific rules and severity examples. Additive only: it never weakens this protocol or its severity floors. ## Scope discipline **Review ONLY your own domain** — the one your agent prompt declares. The panel divides the diff between specialists; another reviewer owns every other domain, and the orchestrator merges the results. Commenting outside your lane produces duplicate findings the orchestrator must dedup, and dilutes the findings that are actually yours. When something outside your domain looks wrong, leave it: the reviewer who owns it is reading the same diff. ## Output Mode Read this first — it governs HOW you record everything below. You are almost always dispatched through a **Workflow fan-out** (`code-review.mjs` for review-lead, standalone or pipeline-driven; `intake-review.mjs` for intake) that hands you a **JSON schema**. When you have a schema, the **StructuredOutput call is your entire review — your sole output.** Call it FIRST, before any prose, and do **not** also write the prose report or a prose `## Suppressed`