agentleFS
caterpi11arcaterpi11ar/giclaw/.agents/skills/diagnosing-bugs/SKILL.md

diagnosing-bugs

Skill9 starsChanged 29 days agoNo licenceView on GitHub

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.

219 other projects use a version of this, 136 of them edited; 34 of 136 edited versions we compared changed its rules; 16 new projects in the last 4 weeks, against 8 the 4 before.

How people change it

34 of 136 edited versions changed its rules, and some changes recur.

Of the 136 edited versions we compared: 72 keep every rule, 30 are an older text, 34 made changes of their own.

Not in older versions

  1. If the redacted output is not enough to diagnose the bug, say so and ask the user.missing from 30 of 30
  2. Write the regression test before the fix, but only if there is a correct seam for it.missing from 1 of 30

Rules people drop

  1. If the redacted output is not enough to diagnose the bug, say so and ask the user.dropped by 18 of 34
  2. When exploring the codebase, read GLOSSARY.md (if it exists) to get a clear mental model of the relevant modules, and check ADRs in the area you're touching.dropped by 15 of 34
  3. Do not proceed until you have reproduced and minimised.dropped by 13 of 34
  4. Differential loop. Run the same input through old-version vs new-version (or two configs) and diff outputs.dropped by 11 of 34
  5. If you catch yourself reading code to build a theory before this command exists, stop: jumping straight to a hypothesis is the exact failure this skill prevents. No red-capable command, no Phase 2.dropped by 11 of 34
  6. Property / fuzz loop. If the bug is "sometimes wrong output", run 1000 random inputs and look for the failure mode.dropped by 10 of 34
  7. Debugger / REPL inspection if the env supports it. One breakpoint beats ten logs.dropped by 10 of 34
  8. If a correct seam exists:dropped by 10 of 34

Rules people add

  1. No red-capable command, no Phase 2.added by 3 of 34
  2. If you catch yourself reading code to build a theory before this command exists,added by 3 of 34
  3. Stop and say so explicitly. List what you tried. Ask the user for: (a) access to whatever environment reproduces it, (b) a captured artifact (HAR file, log dump, screen recording with timestamps), or (c) permission to add temporary instrumentation. …added by 2 of 34
  4. A rule we can't quote: its licence doesn't allow itadded by 2 of 34

We split this file and each edited version into the rules they give an agent and match them by wording. A version that adds no rule of its own and has not changed since this file last did reads as an older text, so what it lacks is not counted as dropped. We keep no past texts of a file, so that is inferred, and an edited version that started from an older text still counts its gaps as drops.

Adopted by

Rising: 16 new projects took it in the last 4 weeks, 2× the 4 weeks before.

Week of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 2 new projectsWeek of Oct 11: 6 new projectsWeek of Oct 18: 4 new projectsWeek of Oct 25: 4 new projectsWeek of Nov 1: 2 new projectsWeek of Nov 8: 6 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read.

Most recently taken up by

Used with

Projects with it also use decision-mapping.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • FabienDehopreSkill

    decision-mapping

    Turn a loose idea into a sequenced map of investigation tickets, then drive them to resolution one at a time.

    Also in 6 projects that use this

The file

Show its rules and text

We split this skill into the rules it gives an agent

14 rules. 12 are common, 1 is distinctive, and 1 is very specific to this project.

  • 12

    Common

    Most of the 157 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 157 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.

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.