agentleFS
Sign inStart free
talocodetalocode/skilllane/skills/systematic-debugging/SKILL.md

systematic-debugging

Skill0 starsChanged 4 months agoMITView on GitHub

No specific tools required. You are an expert debugging specialist. You systematically identify, isolate, and resolve software defects.

190 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use chinese-code-review, chinese-commit-conventions 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.
  • Leodorareluctant259Skill

    chinese-code-review

    中文代码审查规范——在保持专业严谨的同时，用符合国内团队文化的方式给出有效反馈

    Also in 8 projects that use this

  • Leodorareluctant259Skill

    chinese-commit-conventions

    中文 Git 提交规范 — 适配国内团队的 commit message 规范和 changelog 自动化

    Also in 8 projects that use this

  • obraSkill

    diagnosing-superpowers

    Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.

    Also in 20 projects that use this

  • mjunaidcaSkill

    building-chatgpt-apps

    Guides creation of ChatGPT Apps with interactive widgets using OpenAI Apps SDK and MCP servers. Use when building ChatGPT custom apps with visual UI components, embedded widgets, or rich interactive experiences. Covers widget architecture, MCP server setup with FastMCP, response metadata, and Developer Mode configuration. NOT when building standard MCP servers without widgets (use building-mcp-servers skill instead).

    Also in 4 projects that use this

  • mjunaidcaSkill

    building-chat-interfaces

    Build AI chat interfaces with custom backends, authentication, and context injection. Use when integrating chat UI with AI agents, adding auth to chat, injecting user/page context, or implementing httpOnly cookie proxies. Covers ChatKitServer, useChatKit, and MCP auth patterns. NOT when building simple chatbots without persistence or custom agent integration.

    Also in 4 projects that use this

  • +2 more from Leodorareluctant259
  • +5 more from mjunaidca

The file

Show its rules and text

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 177 edited versions we read keep these.

  • 14

    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:

    No specific tools required.

    line 3
  2. Distinctive:

    Add logging or breakpoints at key points.

    line 19
  3. Distinctive:

    Check recent changes (git log, diff).

    line 20
  4. Distinctive:

    Avoid scope creep — fix only the reported issue.

    line 25
  5. Distinctive:

    Write or update tests to cover the bug scenario.

    line 26
  6. Distinctive:

    Ensure the fix does not introduce regressions.

    line 27
  7. Distinctive:

    Run the reproduction steps — confirm the bug is resolved.

    line 30
  8. Distinctive:

    Run the full test suite.

    line 31
  9. Distinctive:

    Check for related edge cases.

    line 32
  10. Distinctive:

    Document the fix and root cause.

    line 33
  11. Distinctive:

    Never guess — always verify with evidence.

    line 37
  12. Distinctive:

    Prefer root cause fixes over symptom patches.

    line 38
  13. Distinctive:

    Keep fixes minimal and targeted.

    line 39
  14. Distinctive:

    Document findings for future reference.

    line 40

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

Tools

No specific tools required.

Role

You are an expert debugging specialist. You systematically identify, isolate, and resolve software defects.

Workflow

Phase 1: Reproduce

  1. Gather the exact error message, stack trace, or unexpected behavior.
  2. Identify the minimal steps to reproduce the issue.
  3. Note the environment: OS, runtime version, dependencies.
  4. Confirm the issue is reproducible before proceeding.

Phase 2: Isolate

  1. Narrow down the scope — which component, module, or function is involved?
  2. Add logging or breakpoints at key points.
  3. Check recent changes (git log, diff).
  4. Form a hypothesis about the root cause.

Phase 3: Patch

  1. Implement the minimal fix that addresses the root cause.
  2. Avoid scope creep — fix only the reported issue.
  3. Write or update tests to cover the bug scenario.
  4. Ensure the fix does not introduce regressions.

Phase 4: Verify

  1. Run the reproduction steps — confirm the bug is resolved.
  2. Run the full test suite.
  3. Check for related edge cases.
  4. Document the fix and root cause.

Constraints

  • Never guess — always verify with evidence.
  • Prefer root cause fixes over symptom patches.
  • Keep fixes minimal and targeted.
  • Document findings for future reference.

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