agentleFS
Sign inStart free
GhostekenGhosteken/agent-harness/skills/debugging-strategies/SKILL.md

debugging-strategies

Skill2 starsChanged 42 days agoMITView on GitHub

Transform debugging from frustrating guesswork into systematic problem-solving with proven strategies, powerful tools, and methodical approaches.

11 other projects use a version of this, 5 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use code-review-excellence.

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

    code-review-excellence

    Master effective code review practices to provide constructive feedback, catch bugs early, and foster knowledge sharing while maintaining team morale. Use when reviewing pull requests, establishing review standards, or mentoring developers.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 11 edited versions we read keep these.

  • 4

    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:

    Document findings and verify the fix.

    line 29
  2. Very specific:

    If detailed playbooks are required, open resources/implementation-playbook.md.

    line 30
  3. Distinctive:

    Use this skill only when the task clearly matches the scope described above.

    line 37
  4. Distinctive:

    Do not treat the output as a substitute for environment-specific validation, testing, or expert review.

    line 38
  5. Distinctive:

    Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

    line 39

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

Debugging Strategies

Transform debugging from frustrating guesswork into systematic problem-solving with proven strategies, powerful tools, and methodical approaches.

Use this skill when

  • Tracking down elusive bugs
  • Investigating performance issues
  • Debugging production incidents
  • Analyzing crash dumps or stack traces
  • Debugging distributed systems

Do not use this skill when

  • There is no reproducible issue or observable symptom
  • The task is purely feature development
  • You cannot access logs, traces, or runtime signals

Instructions

  • Reproduce the issue and capture logs, traces, and environment details.
  • Form hypotheses and design controlled experiments.
  • Narrow scope with binary search and targeted instrumentation.
  • Document findings and verify the fix.
  • If detailed playbooks are required, open resources/implementation-playbook.md.

Resources

  • resources/implementation-playbook.md for detailed debugging patterns and checklists.

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

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