fix-until-green SKILL.md skillA
fix-until-green from ivy00johns/skill-madness is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add ivy00johns/skill-madness/fix-until-green@v1.0.0Pins v1.0.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- ivy00johns/skill-madness
- Path
skills/loops/fix-until-green/SKILL.md- Versions recorded
- 3
- Latest version
- v1.0.0, committed Jun 24, 2026
- First version recorded
- Jun 21, 2026
- Size
- 10,269 bytes
- Repository stars
- 11
- License
- MIT
Drive a failing build to passing in a disciplined loop: run the project's full gate (tests + lint + typecheck), fix one root cause, re-run the whole gate, and repeat until all three exit clean — with a hard iteration cap, no-progress detection, and a rule against cheating the gate green. Use when tests/CI are red and you want them green, when a build wave fails its checks, or as the QE inner loop under an orchestrated build. Trigger on: "fix until green", "make the tests pass", "get CI green…
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
# fix-until-green > **A configuration of [`loop-controller`].** That skill supplies the loop > machinery — primitive selection, the full guardrail stack, state > externalization. This skill supplies the two things specific to "get the build > green": a **mechanical proof** (three exit codes) and the **fix discipline** > that keeps the loop from cheating its way there. Read `loop-controller` for the > guardrails; they're inherited, not repeated here. > > **Why `disable-model-invocation`:** this loop edits and commits code on its own > until a gate passes. You want to *type* `/fix-until-green` (or have the > orchestrator dispatch it) — not have Claude start an autonomous edit loop > because a test happened to fail. ## The 5-part contract | Part | This loop | |---|---| | **trigger** | red suite / CI, a failed build wave, or an explicit `/fix-until-green` (optionally scoped to a path) | | **action** | run the whole gate → read the highest-signal failure → fix **one root cause** → re-run the **whole** gate | | **proof** | `test` exits 0 **AND** `lint` exits 0 **AND** `typecheck` exits 0 — default-FAIL (assume red until all three are observed clean **in the same run**) | …
Read the whole file at its exact version.
How to install
mdr add ivy00johns/skill-madness/fix-until-green@sha256:ec224d3ff89ef60aThe line at the top of this page pins the label v1.0.0, 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_oo7jdnf2yd4dvdy7)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Jun 21, 2026 and Jun 24, 2026, about one every day.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.0 latest | 2026-06-24 | d95a4c1 | 10,269 B | A | view · diff |
| v1.0.0 | 2026-06-21 | ec43f09 | 9,470 B | A | view · diff |
| v1.0.0 | 2026-06-21 | b84e4fc | 9,444 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 (10269 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
ivy00johns/skill-madness · 11 stars · license MIT · pushed 2026-10-25 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_oo7jdnf2yd4dvdy7 GET https://markdownregistry.com/api/v1/resolve?ref=ivy00johns/skill-madness/fix-until-green GET https://markdownregistry.com/api/v1/blob/ec224d3ff89ef60a965e0874e0b794aa9279fbbb5d9641911f7e711199e91a83
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.