Build fix minimal diff

Skill yeaight7/agent-powerups/skills/build-fix-minimal-diff

Use when a build, test, type check, or lint is failing — locally or in CI — and the fix must be the smallest safe diff with no opportunistic refactors or unrelated changes.From its SKILL.md

Install

npx -y skills add yeaight7/agent-powerups --skill build-fix-minimal-diff

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.0 KB, 680 tokens by cl100k_base, as published. Nobody here has run it

Build Fix — Minimal Diff

Fix the failing build, test, or type check. Nothing else.

When to Use

A CI build is red and blocking other work
Tests pass locally but fail in CI — or vice versa
Type errors or lint errors block a commit or pipeline
A previous change broke a test that was passing

Core Rule

Touch only what is broken. Fix the root cause. Rerun. Done.

Any unrelated improvement — even a one-line cleanup — is out of scope for this skill.

Inputs

The exact failing command (e.g., npm test, cargo build, tsc --noEmit, pytest)
The full error output — exact messages and line numbers, not a summary
Current branch state (git status --short, git diff --stat)

Workflow

1. Reproduce

Run the exact failing command and confirm it fails with the same error.

If it does not fail locally:

Check environment differences: tool versions, env vars, installed packages, generated files
Run a clean install (npm ci, pip install -r requirements.txt, etc.) and retry
Document the environment discrepancy instead of guessing at a fix

2. Isolate

Read the error output from the first line — the first error is usually the root cause; later errors are often cascades
Identify the single failure point: file, line number, symbol, or command
Do not start changing code until the root cause is clearly identified

3. Fix

Apply the minimal change that addresses the identified root cause
One change at a time
Do not touch adjacent code, even if it looks wrong — log it as a follow-up
Do not update test expectations to make tests pass unless the expectations were genuinely wrong (i.e., the code behavior is now correct and the test was testing the old — wrong — behavior)

4. Rerun

Run the exact failing command: it must exit 0
Run the full test suite to confirm no regressions introduced

5. Report

FIXED: <what was broken — command and error>
CAUSE: <root cause — specific, not vague>
CHANGE: <file:line — what was changed and why>
VERIFIED: <command run> → exit 0
REGRESSIONS: none / [list]
DEFERRED: <adjacent issues noticed but not touched>

Verification

Exact failing command exits 0 after the fix
Full test suite still passes
No files modified beyond the narrowest fix

Failure Modes

Fixing a cascade error instead of the root cause — go back to step 2
Changing test assertions to match broken implementation — only valid when the test was wrong, never when the code is wrong
Multiple changes at once — revert all but the smallest hypothesis and retry
"While I'm here" scope creep — log it as a follow-up task, do not include it in this fix

Sources / Inspiration

Inspired by Yeachan-Heo/oh-my-codex prompts/build-fixer.md. Rewritten in Agent Powerups style.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most quality gates skills give in 680 tokens

Counted across 1,524 of the 2,830 authors here whose files we hold, read 2026-09-06

Read full output and check exit codein 45 of 1524, across 40 files
Verify output confirms the claimin 44 of 1524, across 39 files
Identify the command that proves the claimin 43 of 1524, across 39 files
Execute the full verification commandin 36 of 1524, across 30 files
Produce a verification reportin 34 of 1524, across 18 files
Review git diff changesin 30 of 1524, across 16 files
Fix build failures immediatelyin 29 of 1524, across 9 files
Group findings by severityin 28 of 1524
State claim only with evidencein 27 of 1524, across 22 files
Verify regression tests with red-green cyclein 26 of 1524, across 22 files
Run the full test suitein 26 of 1524, across 25 files
Run test suite with coveragein 25 of 1524, across 10 files

Said here and by no other author read

Apply the minimal change to fix the root cause
Log unrelated improvements as follow-up tasks

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.