Map codebase context for agents with Ripwire
Use Ripwire to give coding agents deterministic repository maps, task-relevant symbols, blast radius, and test guidance before they edit.
npx skills add agentskillexchange/skills --skill map-codebase-context-for-agents-with-ripwire
Use Ripwire when an agent or operator needs fast, deterministic codebase context before coding, reviewing, debugging, or splitting work. The workflow is to install the local ripwire binary and agent skills, run targeted commands such as ripwire . –for=”task”, ripwire . –pr-context, ripwire . –situ, or the optional MCP server, then feed the ranked symbols, callers, blast radius, quality signals, and suggested tests back into the coding session. Invoke this instead of using a coding product normally when the product is about to spend tokens grepping, reading whole files, guessing impact, or coordinating multiple agents without a shared repository map. The scope boundary is repository-navigation and change-safety evidence for coding agents; it is not a generic C++ library, a generic MCP server card, or a broad static-analysis platform listing.
What this skill actually does
Inputs and prerequisites: Ripwire CLI, local repository checkout, shell access, optional MCP-capable coding agent, optional Codex plugin skills.
Setup notes: Install the Ripwire release binary or build from source, ensure ripwire is on PATH, optionally register the included MCP server with ripwire –mcp and install the bundled agent skills, then run ripwire . –for=”your task” or ripwire . –pr-context from the target repository before editing or reviewing.
Source and verification boundary: use https://github.com/redhat-et/ripwire as the canonical reference before running the workflow; keep commands, API calls, CLI usage, and generated outputs reviewable against that upstream source.
Framework fit: publish this as a Multi-Framework workflow only when the operator can invoke the documented toolchain directly, rather than treating the upstream project as a generic product listing.