debug-helper
Debug assistant for error analysis, log interpretation, and performance profiling. Use when user encounters errors, crashes, or performance issues.
Best use case
debug-helper is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Debug assistant for error analysis, log interpretation, and performance profiling. Use when user encounters errors, crashes, or performance issues.
Teams using debug-helper should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/debug-helper/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How debug-helper Compares
| Feature / Agent | debug-helper | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Debug assistant for error analysis, log interpretation, and performance profiling. Use when user encounters errors, crashes, or performance issues.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Debug Helper Systematic debugging workflow. ## Error Analysis 1. **Read the error** — Full stack trace and error message 2. **Locate** — Find the source file and line ```bash # Search for the error origin grep -rn "ErrorClass\|error_function" src/ ``` 3. **Context** — Read surrounding code (±30 lines) 4. **Reproduce** — Identify minimal reproduction steps 5. **Root cause** — Trace the data flow to find where it goes wrong 6. **Fix** — Minimal change that addresses the root cause 7. **Verify** — Run the failing case to confirm the fix ## Log Analysis 1. Read the log file or output 2. Identify patterns: timestamps, error levels, request IDs 3. Correlate events across log lines 4. Summarize: what happened, when, and why ## Performance Profiling 1. **Measure** — Get baseline numbers first ```bash time <command> ``` 2. **Profile** — Use language-appropriate tools: - Node.js: `--prof`, `clinic.js` - Python: `cProfile`, `py-spy` - Go: `pprof` 3. **Identify** — Find the hotspot (usually 1-2 functions) 4. **Optimize** — Fix the bottleneck 5. **Verify** — Measure again, compare with baseline
Related Skills
write-a-skill
Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill.
web-search
Web search via DuckDuckGo. Use when the user needs to look up current information online.
web-fetch
Fetch a web page and extract readable text content. Use when user needs to retrieve or read a web page.
rust-workspace-bootstrap
Scaffold a production-ready Rust workspace with knope changesets, devenv, and GitHub Actions CI/release workflows. Use when starting a new Rust project or monorepo.
request-refactor-plan
Create a detailed refactor plan with tiny commits via user interview, then file it as a GitHub issue. Use when user wants to plan a refactor, create a refactoring RFC, or break a refactor into safe incremental steps.
quick-setup
Detect project type and generate .pi/ configuration. Use when setting up pi for a new project or when user asks to initialize pi config.
pwsh
PowerShell syntax reference — cmdlets, objects, pipelines, filtering, comparison operators, and Bash-to-PowerShell command equivalents
nushell
Nushell syntax reference for shell commands — variables, pipelines, tables, custom commands, control flow, Bash-to-Nu equivalents, and common gotchas
neubrutalism
Neubrutalism design system skill. Use when building bold UI with thick borders, offset solid shadows, high saturation colors, and minimal border radius.
liquid-glass
Apple Liquid Glass design system. Use when building UI with translucent, depth-aware glass morphism following Apple's design language. Provides CSS tokens, component patterns, dark/light mode, and animation specs.
improve-codebase-architecture
Explore a codebase to find opportunities for architectural improvement, focusing on making the codebase more testable by deepening shallow modules. Use when user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more AI-navigable.
grill-me
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".