Skip to content
Development
Skill

/common-debugging

Troubleshoot systematically using the Scientific Method. Use when debugging crashes, tracing errors, diagnosing unexpected behavior, or investigating exceptions.

From plugin
agent-skills-standard
583200 skills21 agents33 commands1 MCP

Claude Code

$ npx -y skills add hoangnguyen0403/agent-skills-standard --skill common-debugging --agent claude-code

SKILL.md

common-debugging.SKILL.md
name: common-debugging
description: Troubleshoot systematically using the Scientific Method. Use when debugging crashes, tracing errors, diagnosing unexpected behavior, or investigating exceptions.
metadata:
  triggers:
    keywords:
    - debug
    - fix bug
    - crash
    - error
    - exception
    - troubleshooting

Debugging Expert

**Priority: P1 (HIGH)**

Root-Cause Protocol

1. **OBSERVE**: Gather error, logs, repro steps, recent diffs. 2. **REPRODUCE**: Make the failure happen on demand or gather more evidence. 3. **HYPOTHESIZE**: State one hypothesis in plain language. 4. **EXPERIMENT**: Change one variable to prove or kill the theory. 5. **FIX**: Touch code only after root cause proven. 6. **VERIFY**: Re-run the failing case and regression checks.

Red Flags

  • **Stop if you are changing code before repro**: You are guessing.
  • **Stop if fix #2 starts before understanding fix #1**: Re-open root cause.
  • **Stop if "quick patch for now" appears**: Symptom masking starts there.

Rationalization Prevention

  • **"The bug is obvious"**: Obvious bugs still need evidence.
  • **"I already tried a few things"**: That means you need structure.
  • **"It only fails in prod"**: Gather prod evidence, do not invent local myths.
  • **Minimal repro first**: A minimal reproduction beats more random fixes.

Anti-Patterns

  • **No shotgun debugging**: Prove root cause before changing code.
  • **No debug prints in production**: Remove all print/console.log before commit.
  • **No symptom masking**: Fix root cause; never swallow errors without handling.

References

  • [Bug Report Template](references/bug-report-template.md)

Incident pressure checklist

  • For production incidents, reproduce with a production-like replay and state one hypothesis before changing code; stop symptom patches until the root cause is proven.
Read more
@hoangnguyen0403
Ships withagent-skills-standard

The portable standards layer for AI coding agents. Sync once, then work in your own runtime.

583200 skills21 agents1 MCP
Get the whole plugin

Stars on GitHub

Momentum

stars in total
583
Star history of hoangnguyen0403/agent-skills-standard on GitHub, a chart by star-history.com

Other skills on agent-skills-standard.

More skills from other plugins.

brainstorming
Auto-invoked

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…

@obra@obraInstall Skill
ask-matt

ask-matt

Ask which skill or flow fits your situation. A router over the skills in this repo.

skills11d309k
@mattpocock@mattpocockInstall Skill
accessibility
Auto-invoked

accessibility

Design, implement, and audit accessible UI to WCAG 2.2 Level AA across Web, iOS, and Android — semantic ARIA roles and labels,…

ecc13d293k
@affaan-m@affaan-mInstall Skill
compiler-commit

compiler-commit

Use when you want to verify compiler changes and commit with the correct convention. Runs tests, lint, and format, then commits…

react2d252k
@facebook@facebookInstall Skill

Questions about common-debugging.

Which coding agents can use common-debugging?
common-debugging installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.