ripwire-repo-map

# ripwire — deterministic repo map before reading code `ripwire` (v0.4.x at authoring time; the release binary must be on PATH) is a zero-dependency C++23 CLI that builds a ranked, deterministic call graph of any repo in ~1s (parses once, then auto-caches warm). It answers "what to touch, what it breaks, which tests to run" for a fraction of the tokens of grep + whole-file reads. No API key, no daemon, no index server, offline. Invoke it via the terminal tool. ## When to reach for it (instead of blind grep / whole-file reads) - Landing cold in a repo or subsystem — "what's here, how is it organized, what matters" - "Where is the code for X" — a task, feature, or concept in your own words - A change is proposed — what breaks, who calls it, which tests must run - Resuming work after compaction / a new session on in-flight work - Reviewing code you did not write (fresh eyes), or pre-commit change vetting Do NOT use for trivial single-file lookups (plain `rg`/search_files wins) or broad common-word questions — ripwire shines on specific technical asks. ## Core verbs (all take a repo dir; `--help` is authoritative) ```bash ripwire <dir> --report # architecture summary: modules, god-files, cycles, top symbols ripwire <dir> --for="<task in your own words>" # ranked task lens: what to touch first, with 1-hop edges ripwire <dir> --callers=someFunc # who calls it (blast radius) ripwire <dir> --test-gate # which tests must run before committing ripwire <dir> ...