agentleFS
PingPingEPingPingE/ai-content-agents/.claude/skills/auto-fix/SKILL.md

auto-fix

Skill2 starsChanged 9 months agoMITView on GitHub

Auto-fix build errors, lint violations, and type errors with a 2-round QA loop

6 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 6 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 6

    Distinctive

    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:

    Run the quality check pipeline:

    line 24
  2. Distinctive:

    Read the file with the error

    line 34
  3. Distinctive:

    Verify the fix doesn't break other code

    line 37
  4. Distinctive:

    If all issues resolved → report success

    line 42
  5. Distinctive:

    If issues remain → report what needs human attention

    line 43
  6. Very specific:

    Never use any types

    line 59
  7. Distinctive:

    If uncertain, escalate to human

    line 61

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “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

Auto-Fix

Automatically fix build errors, lint violations, and type errors.

Instructions

Round 1: Detect Issues

  1. Run the quality check pipeline:
    • npm run build
    • npm run lint
    • npx tsc --noEmit
  2. Parse output for errors and warnings
  3. Categorize: Critical (blocks deploy), Warning (code quality), Info (style)

Round 2: Fix Issues

For each issue (Critical first, then Warning):

  1. Read the file with the error
  2. Understand the root cause
  3. Apply the fix following codebase patterns
  4. Verify the fix doesn't break other code

Round 3: Re-Verify

  1. Re-run the quality check
  2. If all issues resolved → report success
  3. If issues remain → report what needs human attention
  4. Never attempt a third round — escalate

Output Format

## Auto-Fix Report

### Issues Found: [N] | Fixed: [N] | Remaining: [N]

### Verdict: SUCCESS / PARTIAL / ESCALATED

Rules

  • Two rounds maximum
  • Never use any types
  • Match existing code patterns
  • If uncertain, escalate to human

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.