agentleFS
Sign inStart free
moah0911moah0911/aftermath/skills/build-failure/SKILL.md

build-failure

Skill14 starsChanged 6 days agoMITView on GitHub

Use when compilation, typechecking, bundling, or another build step fails. Read the first error, isolate the hunk, and do not run tests until the build is green. Distinct from a test regression: the code never ran.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. elastic/cli★ 55same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository9 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Stop. No new edits until the first error is read.

    line 16
  2. Distinctive:

    If the build was already red before your edit, say so with evidence instead of claiming you broke it.

    line 21
  3. Distinctive:

    Never "fix" a build by deleting the failing code or suppressing the diagnostic.

    line 37
  4. Very specific:

    If the build fails because a dependency is missing, switch to dependency-failure.

    line 38

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Build Failure

A build failure means the code never reached the tests. Fix the build before interpreting any test result.

Steps

  1. Stop. No new edits until the first error is read.
  2. Paste the first error verbatim, with file and line. Later errors are usually noise from the first one.
  3. Identify the last edit that touches that file or symbol. Diff it.
  4. Fix only that hunk. Do not disable type checks, ignore errors, or loosen compiler flags to get past it.
  5. Re-run the same build command. Green build → run the tests. Still red → use the retry-loop ladder; do not vary flags blindly.
  6. If the build was already red before your edit, say so with evidence instead of claiming you broke it.

Common signatures

ToolSignature
TypeScripterror TS2322, error TS7006
Rusterror[E0308], error[E0433]
Gocannot use ... as, undefined:
Java / KotlinBUILD FAILED, compilation failed
BundlersModule not found, Failed to compile, ELIFECYCLE

Boundaries

  • Build failures are advisory in the plugin: they do not freeze forward edits, because fixing the build requires an edit.
  • Checkpoint auto-revert applies to green→red tests, not build failures.
  • Never "fix" a build by deleting the failing code or suppressing the diagnostic. That is hiding the break.
  • If the build fails because a dependency is missing, switch to dependency-failure.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free