ripwire-find-bug SKILL.md skillA
ripwire-find-bug from redhat-et/ripwire is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add redhat-et/ripwire/ripwire-find-bug@git:20260914.d09bb1bPins git:20260914.d09bb1b in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- redhat-et/ripwire
- Path
skills/ripwire-find-bug/SKILL.md- Versions recorded
- 7
- Latest version
- git:20260914.d09bb1b, committed Sep 14, 2026
- First version recorded
- Aug 31, 2026
- Size
- 8,827 bytes
- Repository stars
- 2,530
- License
- Apache-2.0
You have a SYMPTOM — crash, exception, wrong output, failing test, error string — and don't know which code is responsible. Ranks candidates; a stack trace or sanitizer output maps onto frames innermost-first; 'it worked yesterday' / 'my last edit broke it' → --situ. One clear hit plus one focused read is enough.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Find the bug with ripwire > Nearest neighbours: > • You already know the symbol and just want to understand it → **ripwire-navigate**. > • You want the blast radius / tests for a *change* (not to find a bug) → **ripwire-change-check**. > • Repo-wide quality once-over, no specific symptom → **ripwire-fresh-eyes**. > • "Why don't I see feature X?" and nothing looks broken — the code may be built but compiled/flagged OFF, > not buggy: `ripwire <dir> --flags[=SUBSTR] --legend=compact` (`--flip=NAME` for the blast radius of turning one ON) — > lives in **ripwire-fresh-eyes**, worth a look before you go hunting for a bug that isn't one. `<dir>` = repo root. Calls are warm after the first parse — chain freely. **Pick the branch that matches what you already know**; each converges on the same evidence trail (relevance × maintenance pain × blast radius), so you can escalate between them. **Evidence-sufficiency stop:** escalate only while the responsible code is still ambiguous. If `--for` ranks one file/symbol clearly and a focused source read explains the symptom with a minimal fix, stop …
Read the whole file at its exact version.
How to install
mdr add redhat-et/ripwire/ripwire-find-bug@sha256:8446a5f718c45b0dThe line at the top of this page pins the label git:20260914.d09bb1b, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_ect556stvlxltbjp)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 7 versions of this file, between Aug 31, 2026 and Sep 14, 2026, about one every 2 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260914.d09bb1b latest | 2026-09-14 | d09bb1b | 8,827 B | A | view · diff |
| git:20260913.30a5a3c | 2026-09-13 | 30a5a3c | 8,810 B | A | view · diff |
| git:20260908.8dfd738 | 2026-09-08 | 8dfd738 | 8,657 B | A | view · diff |
| git:20260907.9e1e9f9 | 2026-09-07 | 9e1e9f9 | 8,566 B | A | view · diff |
| git:20260904.72d2605 | 2026-09-04 | 72d2605 | 9,121 B | A | view · diff |
| git:20260902.9670405 | 2026-09-02 | 9670405 | 8,958 B | A | view · diff |
| git:20260831.0e66f12 | 2026-08-31 | 0e66f12 | 8,848 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (8827 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
redhat-et/ripwire · 2,530 stars · license Apache-2.0 · pushed 2026-11-07 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ect556stvlxltbjp GET https://markdownregistry.com/api/v1/resolve?ref=redhat-et/ripwire/ripwire-find-bug GET https://markdownregistry.com/api/v1/blob/8446a5f718c45b0de4ab57911c2c1bcf4baa97229d5bd99b5f4eb25522c6e4f8
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.