ripwire-router

Featured

Start HERE when unsure which ripwire skill fits, or asked 'how do I use ripwire / where do I start'. A moment→skill map, cold start to handoff, plus the two reflexes that leak most: --exemplar before you write, --quality-delta before you call it done. One hop to the right skill.

AI & Automation 1,888 stars 112 forks Updated today Apache-2.0

Install

View on GitHub

Quality Score: 96/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# ripwire router — the moment → skill map Agents route by **moment**, not by feature. Find the row that matches what you're about to do; it names the ONE skill to enter. If you routed wrong, each skill's own routing header sends you one hop to the right one. ## Not sure which verb fits? Ask the tool itself `ripwire <dir> --help-task="<the task in words>"` returns ONE recommended command with the evidence behind the pick (intent, score/margin, repository facts) — or honestly abstains when the evidence is too thin to name a winner. One hop cheaper than reading this whole map: paste the task, run what it recommends. Advice only — it never executes the recommendation. | The moment you're in | The ONE skill | Its opening move | |---|---|---| | **Cold-start** — landed in an unfamiliar repo, "what is this / what matters here" | **ripwire-orient** | `--recall` then `--report` | | **Resuming after a context compaction / a new session on work already in flight** — you have a task but no longer the reasoning that got you here | **ripwire-orient** | rebuild state instead of re-reading files: `--recall="<the task>"` (what past sessions WROTE down) → `--situ` (what the working tree currently has changed + tests to run) → `--notes` (gotchas already paid for). Cheaper and more accurate than re-deriving from source. | | **A pile of DUMPED output, not code** — a `git log`, fetched docs, `<tool> --help`, one oversized reference file, and you need ONE answer out of it | **ripwire-orient** | ...

Details

Author
redhat-et
Repository
redhat-et/ripwire
Created
1 months ago
Last Updated
today
Language
C++
License
Apache-2.0

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Featured

ripwire-orient

Landing COLD in an unfamiliar repo or subsystem, or about to open several files for one question: map first, read only what it ranks highest — main subsystems, entry points, 'how does X work / where is Y'. Also recover context after compaction, retrieve saved docs (--recall), divide code for subagents (--partition), save gotchas (--note-add). NAMED symbol → navigate. Stop at the first rung that answers.

1,888 Updated today
redhat-et
AI & Automation Featured

ripwire-repo-map

Use ripwire CLI to map a repo before reading it.

1,888 Updated today
redhat-et
AI & Automation Featured

ripwire-efficient

A token + accuracy DISCIPLINE for ANY read, not a moment: map before you open files. Reach for it the instant you catch yourself about to open more than ~2 files to figure something out — anywhere in a task. Also the moment you catch yourself typing "let me search the codebase", "let me read that file", or "let me look at a few files first": that sentence IS the trigger. File reads dominate an agent's token cost, and less context is measurably MORE accurate, not just cheaper; a small ranked map beats a fan-out of whole-file reads on both. Code-repair accuracy fell 29% → 3% as context grew 32K → 256K tokens (LongCodeBench), so "read a few more files to be safe" is the instinct this replaces, not a safe default. The reflex is one line: run the cheapest verb that answers the question, then read only the 2-3 files it ranks highest. Fires ALONGSIDE the moment skills (orient, navigate, change-check…), never instead of them. Backed by ripwire (deterministic, on PATH).

1,888 Updated today
redhat-et