Debug

This automates the tedious cycle of adding console.logs, asking users to open DevTools, reproduce bugs, and copy-paste output back to you. Instead, it spins up a local log server that captures runtime evidence server-side so you can read it directly. You instrument code with hypotheses (is userId null? is score a string instead of number?), user reproduces the issue once, and you analyze the logs to confirm or reject each theory. Works across JavaScript, TypeScript, and Python. The workflow is structured around evidence over guessing: no fixes until logs prove the root cause, no cleanup until post-fix logs confirm success. Best for state bugs, async timing issues, and anything where you'd normally be playing telephone with the browser console.

skills.sh installs: 276
GitHub stars: 25
last updated: Jun 3, 2026

View on GitHub

Install

$ npx -y skills add vltansky/debug-skill --skill debug --agent claude-code

Installs into .claude/skills of the current project.

Files

Debug Mode

Fix bugs with runtime evidence, not guesses.

Don't guess → Hypothesize → Instrument → Reproduce → Analyze → Fix → Verify

When to Use

Trigger signals (if you're about to do any of these, use this skill instead):

"Open DevTools Console and check for..."
"Reproduce the bug and tell me what you see"
"Add console.log and let me know the output"
"Click X, open Y, check if Z appears in console"

Example scenario that should trigger this skill:

❌ Without skill (manual, slow):
"I added debug logging. Please:
1. Open the app in browser
2. Open DevTools Console (F12)
3. Open the defect modal and select a defect
4. Check console for [DEBUG] logs
5. Tell me what you see"

✅ With skill (automated):
Logs are captured server-side → you read them directly → no user copy-paste needed

Use when debugging: