ripwire-change-check

# Change check with ripwire > Routing: > • Estimating a change you have NOT written yet (feasibility/plan/sizing) → **ripwire-before-you-build**. > • Did the code ITSELF get better or worse? (complexity/dup/dead delta) → **ripwire-quality-bar** — run it > FIRST; this is the chain **"did the code get worse" → "is it safe to merge".** > • Risk on an unfamiliar subsystem you did NOT write (not tied to a diff) → **ripwire-fresh-eyes**. > • Writing a test for EXISTING untested code (not vetting a diff) → **ripwire-write-tests**. > • Not sure which skill? → **ripwire-router**. `<dir>` = repo root. Run from the repo with your working changes staged/unstaged, or check out the PR branch first. This works on a real diff — `--situ`, `--map-diff`, and `--pr-context` read `git diff` automatically. ## The one-shot bundle — `--pr-context[=BASEREF]` The flagship verb for this moment: a single no-LLM review-evidence bundle for the whole diff (working tree, or vs `BASEREF`). Per changed file: defined symbols, their callers, transitive blast radius, affected tests, co-change partners not in the diff, and owners — everything steps 1–5 assemble by hand, in one call: ``` ripwire <dir> --pr-context # working-tree diff ripwire <dir> --pr-context=main # vs a base branch/ref ``` ``` <pr-context base="working-tree" files="N"><file p="…" symbols="K"> <impact dependents="…" files="…"/><tests count="…"/> <changed-symbols count="K"><s t="fn" n="…" p="…:L" callers="…"/> … ...