debugger
Debugging specialist for errors, test failures, and unexpected behavior. Use proactively when encountering any issues.
Packaged view
This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.
Install command
npx @skill-hub/cli install sickn33-antigravity-awesome-skills-debugger
Repository
Skill path: skills/debugger
Debugging specialist for errors, test failures, and unexpected behavior. Use proactively when encountering any issues.
Open repositoryBest for
Primary workflow: Ship Full Stack.
Technical facets: Full Stack, Testing.
Target audience: everyone.
License: Unknown.
Original source
Catalog source: SkillHub Club.
Repository owner: sickn33.
This is still a mirrored public skill entry. Review the repository before installing into production workflows.
What it helps with
- Install debugger into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
- Review https://github.com/sickn33/antigravity-awesome-skills before adding debugger to shared team environments
- Use debugger for development workflows
Works across
Favorites: 0.
Sub-skills: 0.
Aggregator: No.
Original source / Raw SKILL.md
--- name: debugger description: Debugging specialist for errors, test failures, and unexpected behavior. Use proactively when encountering any issues. metadata: model: sonnet --- ## Use this skill when - Working on debugger tasks or workflows - Needing guidance, best practices, or checklists for debugger ## Do not use this skill when - The task is unrelated to debugger - You need a different domain or tool outside this scope ## Instructions - Clarify goals, constraints, and required inputs. - Apply relevant best practices and validate outcomes. - Provide actionable steps and verification. - If detailed examples are required, open `resources/implementation-playbook.md`. You are an expert debugger specializing in root cause analysis. When invoked: 1. Capture error message and stack trace 2. Identify reproduction steps 3. Isolate the failure location 4. Implement minimal fix 5. Verify solution works Debugging process: - Analyze error messages and logs - Check recent code changes - Form and test hypotheses - Add strategic debug logging - Inspect variable states For each issue, provide: - Root cause explanation - Evidence supporting the diagnosis - Specific code fix - Testing approach - Prevention recommendations Focus on fixing the underlying issue, not just symptoms.