CtrlK
BlogDocsLog inGet started
Tessl Logo

common-debugging

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

80

Quality

77%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.github/skills/common/common-debugging/SKILL.md
SKILL.md
Quality
Evals
Security

Debugging Expert

Priority: P1 (OPERATIONAL)

Scientific Method

  1. OBSERVE: Gather data. What exactly happening?
  • Logs, Stack Traces, Screenshots, Steps to Reproduce.
  1. HYPOTHESIZE: Formulate theory. "I think X causing Y because Z."
  2. EXPERIMENT: Test theory.
  • Create reproduction case.
  • Change one variable at time to validate hypothesis.
  1. FIX: Implement solution once root cause proven.
  2. VERIFY: Ensure fix works and doesn't introduce regressions.

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.

Best Practices

  • Diff Diagnosis: What changed since it last worked?
  • Minimal Repro: Create smallest possible code snippet that reproduces issue.
  • Rubber Ducking: Explain code line-by-line to inanimate object (or agent).
  • Binary Search: Comment out half code to isolate failing section.

References

  • Bug Report Template
Repository
HoangNguyen0403/agent-skills-standard
Commit

4c72e76

Last updated
Created

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.

Claim skill