By redhat-et

Rules for writing and converting formatted output in ripwire's C++ source with its emit helpers, keeping every printed byte identical to the old printf output.

redhat-et/ripwire

Checks whether a working-tree diff or a pull request is safe to merge: blast radius, tests to run, contract breaks, branch conflicts and stranded work.

redhat-et/ripwire

Answers call-graph questions that combine several conditions, such as complex functions that reach a target or untested symbols near main, using ripwire's graph-query mode.

redhat-et/ripwire

Produces a short brief for handing a code subsystem to a teammate or fresh session, using ripwire to rank symbols, expand bodies and surface design docs.

redhat-et/ripwire

Answers questions about a named symbol, such as its callers, what it calls, the path between two symbols or the downstream impact of changing it, using the ripwire CLI.

redhat-et/ripwire

Contributor guide for reading clang optimization remarks while editing ripwire's own C++, deciding between a source change and a build change such as LTO or PGO.

redhat-et/ripwire

Maps an unfamiliar repo or subsystem with the ripwire CLI before reading files, climbing an escalation ladder only until you are oriented.

redhat-et/ripwire

Maps a repository with the ripwire CLI before reading code, ranking what to touch, who calls it and which tests to run.

redhat-et/ripwire

Maintenance risk in code you did NOT write — inheriting a module, planning a refactor, a suspected god object, 'what's gnarly / where's the rot / safe to touch?': hotspots, dead or inactive code…

redhat-et/ripwire

Wire ripwire into an agent as an MCP server — ripwire wrap AGENT (Claude Code, Cursor, Codex, Gemini…) — and choose the server verb mid-task.

redhat-et/ripwire

Security review: (1) vet an untrusted SKILL.md or .mcp.json BEFORE installing it — the injection/exfiltration scanner; CRITICAL blocks the install; (2) audit code on an untrusted-input path (a…

redhat-et/ripwire

Code QUALITY of what YOU just wrote, before you commit or say 'done', or verifying a cleanup: --quality-delta lists what got WORSE in 11 kinds and exits 2 only when pre-existing code got materially…

redhat-et/ripwire

Starting a FEATURE (multi-symbol work): the plan, the API boundary, the scope — how big does this change get — from the codebase's real structure.

redhat-et/ripwire

You have a SYMPTOM — crash, exception, wrong output, failing test, error string — and don't know which code is responsible.

redhat-et/ripwire

About to write ONE symbol (even a 'quick' one-liner) or add a dependency: reuse before you reinvent.

redhat-et/ripwire

Start HERE when unsure which ripwire skill fits, or asked 'how do I use ripwire / where do I start'.

redhat-et/ripwire

Write tests for EXISTING code that has none — 'this is untested, add coverage', 'add a safety net first'; also verify a new test reaches its intended code.

redhat-et/ripwire

Architecture HEALTH and ENFORCEMENT — 'is this a dependency mess / does the UI reach into the database / enforce module boundaries in CI?': cycles, the godfile, propagation cost (how far a touch…

redhat-et/ripwire

A MEASURED performance problem: start from a benchmark, flame graph, perf sample or profiler run, locate the hot symbol the profile names, test structural hypotheses (memory-bound → cache-line data…

redhat-et/ripwire