Best skills for: Debugging
Debugging is where AI coding assistants truly shine—if you know which skills to invoke. For developers on Claude Code, Cursor, or Copilot, the key is selecting skills that guide the AI to reason about root causes, not just patch symptoms. A skill like WebSocket Engineer is gold for tackling real-time communication issues, teaching the model to inspect message flows and latency. Meanwhile, Domain-Driven Design (DDD) helps the AI align with your domain logic, preventing fixes that break business rules. Pitfall: avoid vague prompts like 'fix this bug.' Instead, ask for a hypothesis-driven analysis—'what could cause this null pointer in this DDD aggregate?' The best debugging skills force a structured approach: isolate the symptom, trace the execution path, and validate assumptions. Remember, AI debugging is iterative; use the skill to drill down on logs and error stacks, not just ask for a one-liner fix.
24 skills selected
No Johns Setup Troubleshooter
Development
Diagnoses and fixes common setup issues for No Johns, an AI training framework for Melee. Runs systematic checks on Python 3.12, required packages (libmelee, pyenet), configuration files (Dolphin path, ISO, connect code), Dolphin installation, and arena connectivity. Useful when users encounter errors during initial setup or after updates.
Reflexion - Error Documentation
Development
Captures significant errors encountered during development, including root cause analysis and prevention strategies. Helps build a knowledge base to avoid repeating the same mistakes, especially for non-trivial bugs that required meaningful debugging effort.
ConnectStats Bug Report Analyzer
Development
Downloads and extracts a ConnectStats bug report from the server, then analyzes the user description, app logs, and associated databases (activities, tracks) to identify errors and diagnose issues. It is invoked when a user provides a bug report ID or mentions a bug report.
Structured debugging with session persistence
Development
Structured debugging workflow that uses subagents for isolated investigation, preventing context pollution. It persists sessions, gathers symptoms systematically, and manages checkpoints to resume long debugging sessions efficiently. Helps when debugging complex issues that require deep, iterative exploration without losing progress.
View Shella Logs
Development
View Shella daemon and plugin logs from ~/.local/state/shella/dev.log. Supports filtering by plugin name, error level, or showing recent lines. Useful for debugging issues, checking what happened, or monitoring plugin output.
Log Aggregator
Development
Aggregates logs from systemd services, Docker containers, and application files in known projects. Supports filtering by error/warn levels, tailing, searching, and time ranges. Useful for debugging, monitoring service health, and investigating errors.
Systematic Debugging
Development
Systematically diagnoses and resolves software bugs, test failures, data quality issues, and performance problems using various debugging techniques and tools. Helps when encountering errors, crashes, flaky tests, or unexpected behavior in code, tests, data pipelines, or ML models. Covers strategies like isolation, binary search, git bisect, and specialized debugging for flaky tests and data pipelines.
Systematic Bug Fix Workflow
Development
Executes a systematic bug fix workflow: structured investigation, regression test creation, fix implementation, and a formal report in specs/bugfixes/. Automatically handles Transit tickets and branch management. Useful for bugs requiring thorough analysis and full documentation.
Grove Logging Best Practices
Development
A skill for adding NDJSON debug record events to Grove's Rust TUI. Covers wide event design with rich context, event/kind identity pairs, data fields, timing at boundaries, and zero-cost null logger usage. Use when adding new log events, reviewing logging code, or designing instrumentation for new features.
Code Investigation
Development
Investigate codebase issues, debug problems, or analyze patterns using tools like Read, Grep, Glob, and Bash. It helps developers trace data flow, identify root causes of bugs, or understand code structure systematically.
Bug Fix Workflow
Development
Fixes a specific bug or problem in the codebase by either applying an immediate fix or creating a plan first. It checks for an existing fix plan, investigates using project context and past patches, and always suggests test coverage and adds logging. Use when encountering error messages, unexpected behavior, or when asked to debug.
Systematic Debugging
Development
Systematic debugging with hypothesis-driven investigation. Use when something is broken, tests fail, or errors need investigation. The process includes assessing the issue, isolating the root cause with hypotheses, applying minimal fixes, and adding regression tests to prevent recurrence.
Python Functional Bug Debugging
Development
Investigates functional bugs in Python using specifications, logs, and observed behavior. Useful when a feature isn't working as specified, to analyze runtime errors, or to scope a problem before implementing a fix.
PR Review Pipeline Debugging
Development
Diagnoses why a specific PR review is failing or not triggering in the claude-code-reviewer service. Traces the PR through the full pipeline: state, errors, review history, skip reasons, and simulation of the review gating logic. Useful when a PR is not receiving a review or a review fails unexpectedly.
Systematic Debugging
Development
Diagnose bugs systematically before proposing fixes. Use when something is broken, failing, erroring, or not working as expected. This skill guides through reproduction, isolation, hypothesis testing, and produces a structured diagnosis with evidence.
Local Development
Development
Provides commands for running functions locally (npx nx run functions:serve), the web app (npx nx run maple-spruce:serve), and Storybook. Covers troubleshooting emulator issues, such as missing .env files, with fixes. Helpful when developing locally and debugging emulator problems.
Quick Bug Fix Workflow
Development
Analyzes code to identify and fix bugs directly without creating plans. Adds logging for verification and suggests test coverage to prevent regression. Best suited for reported bugs, errors, or unexpected behavior.
Systematic Debugging
Development
A structured debugging methodology with a decision tree for reproducing, isolating, and tracing bugs. Helps developers systematically diagnose issues by comparing environments, tracing data flow, and performing binary search. Useful when investigating bugs, crashes, or unexpected behavior.
Capability Check
Development
Check whether a given action is feasible and identify what blocks it. Useful when verifying permissions, diagnosing why a command fails, or determining if a tool like iMessage or calendar access is available. Provides commands to test each capability and a troubleshooting flow.
Systematic Debugging
Development
Provides a structured five-phase debugging workflow: understand, reproduce, isolate, fix, and document. Guides through writing failing tests, binary search isolation, minimal fixes, and regression tests. Most useful when tackling complex or non-obvious bugs that require a systematic approach.
Add Bug Branch
Development
Creates a new bug branch from an existing project branch by guiding the user through adding a single debugging challenge. Helps generate debugging exercises with a run.sh script that reproduces the failure.
Mermaid Diagrams
Development
Creates, validates, and troubleshoots Mermaid.js diagrams for flowcharts, sequence diagrams, class diagrams, ER diagrams, state diagrams, Gantt charts, and other visualizations. Uses the rp1 CLI tool for syntax validation and provides structured error feedback for automatic repair. Useful when generating diagrams in markdown or debugging diagram syntax errors.
AppSignal Error Analysis
Development
Use the AppSignal CLI to fetch and analyze error incidents and samples. Supports listing open incidents, retrieving detailed backtraces and context, and managing incident status. Helps when debugging errors, investigating exceptions, or when the user mentions AppSignal.
Stripe Testing and Debugging
Development
Test and debug Stripe payment integrations end-to-end. Simulate payment flows, verify webhook handling, diagnose failed charges, and validate subscription lifecycle. Useful when ensuring Stripe integrations work correctly in development or production.
How to choose
- How are these skills selected?
- Each skill is curated and verified by the Skills Guides editorial team. We run a security and quality review on every entry, so only verified skills appear in this selection.
- What do the security ratings mean?
- We label skills Safe, Caution or Risky based on our security analysis — checking for prompt-injection risks, requested permissions and other red flags. The rating gives you an at-a-glance sense of how much trust a skill warrants.
- How do I install a skill?
- Open any skill page and follow its install instructions for your tool — Claude Code, Cursor or Copilot. Each skill lists the exact steps so you can get it running in a couple of minutes.