SkillAgentSearch skills...

debug

Debug issues by investigating logs, database state, and git history

Install / Use

npx skills add parcadei/Continuous-Claude-v3 --skill debug

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

83/100

Supported Platforms

Universal

Our assessment of debug

debug scores 83/100 on our quality scale, 491st of 604 Data & Analytics skills we index.

Its SKILL.md is 5.2 KB long, well organised into 16 sections with 11 code examples: a solid amount of guidance for an agent.

With 3,943 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
20/20
Description
12/15
Adoption
15/20
Freshness
11/15

Maintenance, license and trust

  • The repository was last updated about 10 months ago. That is recent enough to be usable, but agent tooling moves fast, so check the instructions against your agent's current version.
  • Our last check on 2026-11-06 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 94/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-01. Automated pattern scan on 2026-10-01. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

debug compared with similar skills

All 4 of these similar skills score higher than debug; compare them before choosing.

SkillScoreStarsUpdatedFormat
debug (this skill)by parcadei833.9k10mo agoSKILL.md
Agent-Reachby Panniantong100112.3k8d agoCLAUDE.md
x402by browser-use100121.0k3d agoSKILL.md
algorithmic-artby anthropics100177.9k55d agoSKILL.md
pptxby anthropics100177.9k55d agoSKILL.md

Frequently asked questions

How do I install debug?
Run npx skills add parcadei/Continuous-Claude-v3 --skill debug. The install tabs above show the steps for each supported agent.
Which AI agents does debug work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is debug safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 94/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is debug still maintained?
The repository was last updated about 10 months ago. That is recent enough to be usable, but agent tooling moves fast, so check the instructions against your agent's current version.

name: debug description: Debug issues by investigating logs, database state, and git history

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.

Environment Information

You have access to these key locations and tools:

Logs:

  • Application logs (check project-specific locations)
  • Common locations: ./logs/, ~/.local/share/{app}/, /var/log/

Database (if applicable):

  • SQLite databases can be queried with sqlite3
  • Check project config for database locations

Git State:

  • Check current branch, recent commits, uncommitted changes
  • Similar to how commit and describe_pr commands work

Service Status:

  • Check running processes: ps aux | grep {service}
  • Check listening ports: lsof -i :{port}

Process Steps

Step 1: Understand the Problem

After the user describes the issue:

  1. Read any provided context (plan or ticket file):

    • Understand what they're implementing/testing
    • Note which phase or step they're on
    • Identify expected vs actual behavior
  2. Quick state check:

    • Current git branch and recent commits
    • Any uncommitted changes
    • When the issue started occurring

Step 2: Investigate the Issue

Spawn parallel Task agents for efficient investigation:

Task 1 - Check Recent Logs:
Find and analyze the most recent logs for errors:
1. Find latest logs: ls -t ./logs/*.log | head -1 (or project-specific location)
2. Search for errors, warnings, or issues around the problem timeframe
3. Note the working directory if shown
4. Look for stack traces or repeated errors
Return: Key errors/warnings with timestamps
Task 2 - Database State (if applicable):
Check the current database state:
1. Locate database file (check project config)
2. Connect: sqlite3 {database_path}
3. Check schema: .tables and .schema for relevant tables
4. Query recent data based on the issue
5. Look for stuck states or anomalies
Return: Relevant database findings
Task 3 - Git and File State:
Understand what changed recently:
1. Check git status and current branch
2. Look at recent commits: git log --oneline -10
3. Check uncommitted changes: git diff
4. Verify expected files exist
5. Look for any file permission issues
Return: Git state and any file issues

Step 3: Present Findings

Based on the investigation, present a focused debug report:

## Debug Report

### What's Wrong
[Clear statement of the issue based on evidence]

### Evidence Found

**From Logs**:
- [Error/warning with timestamp]
- [Pattern or repeated issue]

**From Database** (if applicable):
```sql
-- Relevant query and result
[Finding from database]

From Git/Files:

  • [Recent changes that might be related]
  • [File state issues]

Root Cause

[Most likely explanation based on evidence]

Next Steps

  1. Try This First:

    [Specific command or action]
    
  2. If That Doesn't Work:

    • Restart relevant services
    • Check browser console for frontend errors
    • Run with debug flags enabled

Can't Access?

Some issues might be outside my reach:

  • Browser console errors (F12 in browser)
  • MCP server internal state
  • System-level issues

Would you like me to investigate something specific further?


## Important Notes

- **Focus on manual testing scenarios** - This is for debugging during implementation
- **Always require problem description** - Can't debug without knowing what's wrong
- **Read files completely** - No limit/offset when reading context
- **Think like `commit` or `describe_pr`** - Understand git state and changes
- **Guide back to user** - Some issues (browser console, MCP internals) are outside reach
- **No file editing** - Pure investigation only

## Quick Reference

**Find Latest Logs**:
```bash
ls -t ./logs/*.log | head -1
# Or check project-specific log locations

Database Queries (SQLite):

sqlite3 {database_path} ".tables"
sqlite3 {database_path} ".schema {table}"
sqlite3 {database_path} "SELECT * FROM {table} ORDER BY created_at DESC LIMIT 5;"

Service Check:

ps aux | grep {service_name}
lsof -i :{port}

Git State:

git status
git log --oneline -10
git diff

Remember: This command helps you investigate without burning the primary window's context. Perfect for when you hit an issue during manual testing and need to dig into logs, database, or git state.

Related Skills

View on GitHub
GitHub Stars3.9k
CategoryData
Updated9mo ago
Forks303

Languages

Python

Trust signals

94/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 low
debug — Universal Skill: Install & Safety Check | SkillAgent