AgentStack
SKILL verified MIT Self-run

Debug

skill-kriscard-skills-debug · by kriscard

>-

No reviews yet
0 installs
16 views
0.0% view→install

Install

$ agentstack add skill-kriscard-skills-debug

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Debug? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Debug

Systematic root-cause analysis — reproduce, isolate, hypothesize, fix, verify.

Process

  1. Read the error — full message, stack trace, error code. Don't skip this.
  2. Reproduce reliably — minimal steps before touching any code.
  3. Isolate — binary search via git bisect, comment blocks, or minimal repro.
  4. Hypothesize — one specific theory. Don't change multiple things at once.
  5. Test hypothesis — add logging, use debugger, modify code.
  6. Apply minimal fix — smallest change that addresses root cause, not symptoms.
  7. Verify — confirm fix works and no regressions.

Diagnosis Checklist

Start here before touching code:

  • [ ] Read the full error message — it often tells you exactly what's wrong
  • [ ] Check recent changes: git log --oneline -10 / git diff HEAD~1
  • [ ] Check logs around time of failure
  • [ ] Verify environment matches expected (versions, env vars, config)
  • [ ] Could this be a race condition or timing issue?
  • [ ] Is this intermittent or consistent?

Reproduction:

# Find the commit that introduced it
git bisect start
git bisect bad HEAD
git bisect good 

Strategic logging:

// Entry/exit with parameters — temporary, remove after fix
console.log('[debug] functionName called', { param1, param2 });
// ...
console.log('[debug] functionName result', { result });

Anti-Patterns

  • Don't make random changes hoping something fixes it — form a hypothesis first
  • Don't fix symptoms without understanding root cause
  • Don't debug in production without safeguards
  • Don't leave debug logs or breakpoints in committed code
  • Don't trust your mental model — read the actual code

Output

## Root Cause
[What actually caused the issue]

## Evidence
- [Log excerpt / stack trace / variable state]

## Fix
`file:line`
```diff
- broken code
+ fixed code

Why this fixes it: [reasoning]

Prevention

  • [Recommendation to avoid recurrence]

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [kriscard](https://github.com/kriscard)
- **Source:** [kriscard/Skills](https://github.com/kriscard/Skills)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.