ripwire-before-you-build SKILL.md skillA
ripwire-before-you-build 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-before-you-build@git:20260913.30a5a3cPins git:20260913.30a5a3c 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-before-you-build/SKILL.md- Versions recorded
- 6
- Latest version
- git:20260913.30a5a3c, committed Sep 13, 2026
- First version recorded
- Aug 11, 2026
- Size
- 7,985 bytes
- Repository stars
- 2,530
- License
- Apache-2.0
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. Implementing an EXISTING interface? --lego=Iface lists its contract and current implementors. ONE standalone symbol → reuse-first. A small feature with an obvious home needs none of this.
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
# Before you build — with ripwire > Routing: > • Writing ONE symbol (fn/class/helper) and want to reuse rather than reinvent → **ripwire-reuse-first**. > • You've already written the change and want the pre-submit check → **ripwire-change-check**. > • You want to judge whether the code you wrote got better/worse → **ripwire-quality-bar**. > • Restructuring EXISTING code (not new work) → **ripwire-fresh-eyes**. > • Not sure which skill? → **ripwire-router**. `<dir>` = repo root. `FEATURE`/`APPROACH` = your task in 2–4 plain words; `SYM` = a representative symbol. Run only the sections your question needs — they share the same building blocks. ## Common first move — recall + reusable blocks Almost every section starts here; do it once. **One-call shortcut:** `ripwire <dir> --pack-task="FEATURE" --legend=compact` assembles the recall + `--for` ranking + top bodies + caller signatures + notes + `tests_to_run` into ONE bundle under one token budget — reach for it first instead of firing the calls below one at a time; drop to the individual calls only when you need a specific section's full output. …
Read the whole file at its exact version.
How to install
mdr add redhat-et/ripwire/ripwire-before-you-build@sha256:76a3d401559b3ecfThe line at the top of this page pins the label git:20260913.30a5a3c, 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_kdrbmsyetfvpp7ox)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 6 versions of this file, between Aug 11, 2026 and Sep 13, 2026, about one every 6 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260913.30a5a3c latest | 2026-09-13 | 30a5a3c | 7,985 B | A | view · diff |
| git:20260910.908110a | 2026-09-10 | 908110a | 7,730 B | A | view · diff |
| git:20260910.d1e5176 | 2026-09-10 | d1e5176 | 7,711 B | A | view · diff |
| git:20260910.29ae28d | 2026-09-10 | 29ae28d | 7,671 B | A | view · diff |
| git:20260907.9e1e9f9 | 2026-09-07 | 9e1e9f9 | 7,688 B | A | view · diff |
| git:20260811.f63a32d | 2026-08-11 | f63a32d | 8,593 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 (7985 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_kdrbmsyetfvpp7ox GET https://markdownregistry.com/api/v1/resolve?ref=redhat-et/ripwire/ripwire-before-you-build GET https://markdownregistry.com/api/v1/blob/76a3d401559b3ecff8b57363fd72dd11277dd34e796306db2146e7746203ab3a
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.