Debug

When you hit a bug during manual testing and need to figure out what's happening without burning your main context window, this spawns parallel tasks to investigate logs, database state, and git history. It reads recent application logs for errors, queries SQLite databases for stuck states, and checks what changed in your git history. The output is a structured debug report with evidence, root cause analysis, and next steps. Nice for those moments when something breaks and you need to methodically trace through logs and recent commits without cluttering up your implementation context. Won't help with browser console errors or MCP internals, but it handles the server side investigation work competently.

skills.sh installs: 509
GitHub stars: 3.9K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add parcadei/continuous-claude-v3 --skill debug --agent claude-code

Installs into .claude/skills of the current project.

Files

Debug

You are tasked with helping debug issues during manual testing or implementation. This command allows you to investigate problems by examining logs, database state, and git history without editing files. Think of this as a way to bootstrap a debugging session without using the primary window's context.

Initial Response

When invoked WITH a plan/ticket file:

I'll help debug issues with [file name]. Let me understand the current state.

What specific problem are you encountering?
- What were you trying to test/implement?
- What went wrong?
- Any error messages?

I'll investigate the logs, database, and git state to help figure out what's happening.

When invoked WITHOUT parameters:

I'll help debug your current issue.

Please describe what's going wrong:
- What are you working on?
- What specific problem occurred?
- When did it last work?

I can investigate logs, database state, and recent changes to help identify the issue.