agentleFS
sainzssainzs/santiagosainz-skills/skills/core/debug/SKILL.md

debug

Skill1 starsChanged 3 months agoMITView on GitHub

Debug a failing command, bug, flake, runtime error, wrong output, or performance regression with evidence: reproduce, minimize, hypothesize, instrument, fix, and regression-test. Use when the user asks to debug, diagnose, fix a failure, or use debug-loop.

191 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use add-discord, add-slack and 10 more.

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.
  • MicrosoftSkill

    add-discord

    Add Discord bot channel integration via Chat SDK.

    Also in 11 projects that use this

  • MicrosoftSkill

    add-slack

    Add Slack channel integration via Chat SDK.

    Also in 11 projects that use this

  • +10 more from microsoft

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 176 edited versions we read keep these.

  • 10

    Distinctive

    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:

    Do one job: turn a symptom into root cause, fix, and regression proof.

    line 12
  2. Distinctive:

    Keep output bounded: inspect high-signal tails, focused files, and direct repros.

    line 14
  3. Distinctive:

    Use shell and repo-native tools first.

    line 15
  4. Distinctive:

    After two identical failures, change hypothesis or instrumentation.

    line 16
  5. Distinctive:

    Use for failing tests, CI failures, crashes, hangs, flakes, broken UI flows, bad output, slow paths, and environment drift.

    line 20
  6. Distinctive:

    Add temporary instrumentation only when observation is otherwise impossible.

    line 28
  7. Distinctive:

    Add or identify a regression proof and rerun the original repro.

    line 30
  8. Distinctive:

    Do not guess from logs alone when a repro is available.

    line 34
  9. Distinctive:

    Do not widen the fix until the local cause is understood.

    line 35
  10. Distinctive:

    Treat hangs and concurrency failures as first-class symptoms.

    line 36

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

debug

Find root cause before changing code.

Unix/Pi Contract

  • Do one job: turn a symptom into root cause, fix, and regression proof.
  • Consume an exact repro, logs, runtime state, and code path; emit cause, patch, and proof.
  • Keep output bounded: inspect high-signal tails, focused files, and direct repros.
  • Use shell and repo-native tools first; use heavier tooling only when it improves observation.
  • After two identical failures, change hypothesis or instrumentation.

Use

Use for failing tests, CI failures, crashes, hangs, flakes, broken UI flows, bad output, slow paths, and environment drift.

Workflow

  1. Reproduce the symptom with the exact command, URL, or workflow.
  2. Minimize to the smallest failing surface.
  3. State one current hypothesis and the evidence that would disprove it.
  4. Inspect the code path and runtime state that can affect the symptom.
  5. Add temporary instrumentation only when observation is otherwise impossible; remove it before finishing.
  6. Fix the root cause, not just the observed error string.
  7. Add or identify a regression proof and rerun the original repro.

Guardrails

  • Do not guess from logs alone when a repro is available.
  • Do not widen the fix until the local cause is understood.
  • Treat hangs and concurrency failures as first-class symptoms; use timeouts, logs, and serialized repros.
  • Separate pre-existing unrelated failures from failures caused by the edit.

Output

Return:

  1. Symptom and repro.
  2. Root cause.
  3. Fix.
  4. Regression proof.
  5. Commands and results.
  6. Remaining risks or external blockers.

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.