Debugging
Systematic debugging that identifies root causes rather than treating symptoms. Uses sequential thinking for complex analysis, web search for research, and structured investigation to avoid circular reasoning and whack-a-mole fixes.
Install
npx skills add ratacat/claude-skills --skill debugginggit clone --depth 1 https://github.com/ratacat/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/skills/debugging ~/.claude/skills/debuggingPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Debugging ## Quickstart 1. Capture exact repro, scope, and recent changes 2. Isolate components/files; trace path to failure 3. Research exact error; check official docs 4. Compare failing vs working patterns; form a testable hypothesis 5. Verify with minimal test; apply minimal fix across all instances; validate ## When to Use This Skill Use debugging when: - A bug has no obvious cause or has been "fixed" before but returned - Error messages are unclear or misleading - Multiple attempted fixes have failed - The issue might affect multiple locations in the codebase - Understanding the root cause is critical for proper resolution Skip this skill for: - Simple syntax errors with obvious fixes - Trivial typos or missing imports - Well-understood, isolated bugs with clear solutions ## Core Anti-Patterns to Avoid Based on documented failures in AI debugging, explicitly avoid: 1. **Circular Reasoning**: Never propose the same fix twice without learning why it failed 2. **Premature Victory**: Always verify fixes were actually implemented and work 3. **Pattern Amnesia**: Maintain awareness of established code patterns throughout the session 4. **Context Overload**: Use the 50% rule - restart conversation when context reaches 50% 5. **Symptom Chasing**: Resist fixing error messages without understanding root causes 6. **Implementation Before Understanding**: Never jump to code changes before examining existing patterns ## UNDERSTAND (10-step checklist)
Details
- Skill name
debugging- Repository
- ratacat/claude-skills
- Path
skills/debugging/SKILL.md- Repo updated
- 11 February 2026
FAQ
What does the Debugging skill do?
Systematic debugging that identifies root causes rather than treating symptoms. Uses sequential thinking for complex analysis, web search for research, and structured investigation to avoid circular reasoning and whack-a-mole fixes.
How do I install the Debugging skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add ratacat/claude-skills --skill debugging. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Debugging popular?
It lives in ratacat/claude-skills, which has 59 GitHub stars and 10 forks.
Related skills
Skill Creator
59ratacat/claude-skills
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Codex's capabilities with specialized knowledge, workflows, or tool integrations.
Skill Installer
59ratacat/claude-skills
Install Codex skills into $CODEX_HOME/skills from a curated list or a GitHub repo path. Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo (including private repos).
Agent Browser
59ratacat/claude-skills
Browser automation using Vercel's agent-browser CLI. Use when you need to interact with web pages, fill forms, take screenshots, or scrape data. Alternative to Playwright MCP - uses Bash commands with ref-based element selection. Triggers on "browse website", "fill form", "click button", "take screenshot", "scrape page", "web automation".
Design Patterns
59ratacat/claude-skills
Use when designing software architecture, refactoring code structure, solving recurring design problems, or when code exhibits symptoms like tight coupling, rigid hierarchies, scattered responsibilities, or difficult-to-test components. Also use when choosing between architectural approaches or reviewing code for structural improvements.
Data Systems Architecture
59ratacat/claude-skills
Use when designing databases for data-heavy applications, making schema decisions for performance, choosing between normalization and denormalization, selecting storage/indexing strategies, planning for scale, or evaluating OLTP vs OLAP trade-offs. Also use when encountering N+1 queries, ORM issues, or concurrency problems.
Dhh Rails Reviewer
59ratacat/claude-skills
Use this agent when you need a brutally honest Rails code review from the perspective of David Heinemeier Hansson. This agent excels at identifying anti-patterns, JavaScript framework contamination in Rails codebases, and violations of Rails conventions. Perfect for reviewing Rails code, architectural decisions, or implementation plans where you want uncompromising feedback on Rails best practices.\ \ <example>\ Context: The user wants to review a recently implemented Rails feature for adherence to Rails conventions.\ user: "I just implemented a new user authentication system using JWT tokens
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.