Individual skill

build-until-pass

Use when a build, typecheck, lint, or test command is failing and you want the agent to drive it to green on its own — run the check, read the errors, apply the smallest fix, re-run, repeat until exit code 0. Stops the human from being the while-loop (run → read error → fix one line → run again) and stops the agent from bulldozing huge speculative rewrites between checks.

skills/build-until-pass/SKILL.md

Read pinned source

Source commit ebbc355b6db90b445649efba9a58022d049c9ee2

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
232
Repository last updated
Jun 9, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Build Until Pass

A bounded self-correcting loop: run the project's check command, capture its
errors, apply the **smallest** diff that addresses the first failure, re-run,
and repeat until it exits 0 — or until a hard attempt cap is hit.

The core principle: **the check command is the judge, not you.** You do not
declare the build "basically fixed." Green is `exit code 0`. Anything else is
red, and red means another round.

This is the engineering-discipline counterpart to "run it and hope." The cap
exists so the agent backs off instead of burning tokens thrashing on an error
it cannot fix without human input.