judgelisted

# Judge — verify before commit You are the first-line author. This skill spawns the second opinion. ## When to trigger Run this skill BEFORE your final Edit / Write on any of these: - a function signature change - a refactor that touches more than one file - any change that introduces a new public API, schema, or route - any change the user flags as "important" or "risky" - explicit "verify", "double-check", "review before we commit" requests Skip for: - typos / formatting / single-character edits - tests you're writing for an existing behavior - changes the user has already reviewed in the same turn ## How to run the judge Step 1. **Gather structural evidence** about the change. Call these (from jcodemunch) on the symbols you're about to touch: - `get_changed_symbols` — map your planned diff to the exact symbols added / modified / removed. - `get_blast_radius` — depth-weighted impact, with source snippets. - `find_references` (jcodemunch) and/or `find_referencing_symbols` (serena) — who else calls this symbol. - `get_untested_symbols` — flags changes to functions with no test coverage. - `get_pr_risk_profile` — composite score (0.0–1.0) + recommendations. Step 2. **Spawn an independent reviewer** using Claude Code's Agent tool. Use `subagent_type: "code-reviewer"` if available; otherwise `general-purpose`. The prompt you hand it MUST be self-contained — the subagent has no memory of this conversation. Template: ``` Independent review of a proposed change.