AgentStack
Sign in Publish
MCP servers Skills Toolkits Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Vibe Debugging Journal

skill-ash1794-vibe-engineering-debugging-journal · by ash1794

Records resolved bugs in a persistent journal — symptom, root cause, difficulty, fix, prevention. Organized by category for future reference.

↗ Repository
— No reviews yet
0 installs
12 views
0.0% view→install

Install

$ agentstack add skill-ash1794-vibe-engineering-debugging-journal

✓ 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 Vibe Debugging Journal? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

vibe-debugging-journal

Bugs come in patterns. Recording them prevents re-investigation.

When to Use This Skill

  • After resolving a non-trivial bug (took >10 minutes to find)
  • After finding a bug that was hard to reproduce
  • After debugging something where the root cause was surprising
  • When you notice a bug pattern repeating

When NOT to Use This Skill

  • Trivial bugs (typos, missing imports)
  • Bugs with immediately obvious causes
  • Build/configuration issues (not really bugs)

Steps

  1. Categorize the bug:
  • Concurrency (race conditions, deadlocks, ordering)
  • State Management (stale state, missing updates, cache invalidation)
  • Type/Validation (type errors, missing validation, edge cases)
  • Integration (API mismatch, version incompatibility, protocol errors)
  • Environment (platform-specific, config, deployment)
  • UI/Rendering (layout, hooks, lifecycle)
  1. Record in structured format:
### [Category]: [Short description]
**Date**: [date]
**Symptom**: [What was observed]
**Root Cause**: [The actual problem]
**Why Hard to Find**: [What made debugging difficult]
**Fix**: [What was changed]
**Prevention**: [How to prevent recurrence]
**Files**: [affected files]
  1. Save to persistent storage:
  • Project: docs/debugging-journal.md or DEBUGGING.md
  • Memory: Claude auto-memory or MCP
  1. Cross-reference — If this relates to an existing journal entry, link them

Output Format

Present the entry for user confirmation, then save. Keep entries concise (5-10 lines each).

Source & license

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

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

Reviews

No reviews yet — be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in AI & ML