agentleFS
Sign inStart free
Asno-devAsno-dev/apex/skills/bug-patch/SKILL.md

bug-patch

Skill1 starsChanged 5 months agoMITView on GitHub

Invoke when user shares a GitHub issue, bug report, error log, or failing test. "this is failing", "fix this issue", "patch this bug", "issue report", "bug report", "GitHub issue", "failing test". SDLC categories: Program Repair, Defect Detection, Software Maintenance. SWE-Bench class output — correct, runnable patches.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Must not break existing tests

    line 22
  2. Distinctive:

    Must be minimum change that fixes the issue

    line 23
  3. Distinctive:

    Must be applicable with: git apply patch.diff

    line 24
  4. Distinctive:

    Test must fail before patch, pass after patch

    line 25

≈ “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

Bug Patch Protocol (SWE-Bench Class)

  1. READ issue description completely
  2. LOCATE relevant code (ask or search)
  3. REPRODUCE failure condition mentally (or actually if shell available)
  4. ISOLATE root cause — not a symptom, the cause
  5. WRITE minimal patch (diff format preferred)
  6. WRITE regression test — proves patch works
  7. OUTPUT patch + test + one-line explanation of root cause

Patch quality (SWE-Bench criteria):

  • Must not break existing tests
  • Must be minimum change that fixes the issue
  • Must be applicable with: git apply patch.diff
  • Test must fail before patch, pass after patch

Output:

```diff
[the patch]

[test that fails before, passes after] Root cause: [one line]

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