skills.rest
KaimingWan
KaimingWanCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

debug

Reproduce software bugs and analyze root causes with knowledge base integration.

103|15|Updated Feb 6, 2026
Search Tags:#code analysis#debugging#troubleshooting#root cause analysis#bug fixing
One-click install
npx skills add https://github.com/KaimingWan/oh-my-claude-code --skill debug-kaimingwan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/KaimingWan/oh-my-claude-code/tree/main/commands
Command: npx skills add https://github.com/KaimingWan/oh-my-claude-code --skill debug-kaimingwan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you systematically identify and fix bugs in your code, ensuring software stability and reliability.

Core Features & Use Cases

  • Bug Reproduction: Ensures the bug is consistently reproducible before attempting a fix.
  • Root Cause Analysis: Guides the AI to find the fundamental reason for the bug, not just a superficial patch.
  • Knowledge Base Integration: Checks existing lessons learned for similar issues, preventing repeated mistakes.
  • Use Case: When a user reports an intermittent crash, this skill will first work to reliably trigger the crash, then analyze the execution path to pinpoint the exact line of code causing the failure.

Quick Start

Use the debug skill to reproduce and fix the bug described in the attached error log.

Frequently Asked Questions about debug

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I systematically find the root cause of an intermittent software crash?▼

Systematic debugging identifies the root cause of a software crash by first working to reliably reproduce the bug. It then analyzes the execution path to pinpoint the exact failure point, preventing superficial patches and ensuring long-term software stability.

What is the best way to debug code without applying superficial patches?▼

The best way to debug code without superficial patches is performing thorough root cause analysis. This process finds the fundamental reason for the bug, ensuring the fix addresses the underlying issue rather than just masking the symptoms.

How does root cause analysis prevent recurring bugs in software troubleshooting?▼

Root cause analysis prevents recurring bugs by integrating with a knowledge base of lessons learned. It checks existing documentation for similar issues, avoiding repeated mistakes and ensuring past findings inform the current investigation.

Can I use an error log to reproduce and fix a bug?▼

Yes, you can use an error log to reproduce and fix a bug. The debugging process facilitates bug reproduction from the log details, allowing you to consistently trigger the issue before attempting a detailed root cause analysis and fix.

How do I document findings for complex software issues?▼

You document findings for complex software issues during the detailed investigation phase of debugging. This process systematically records the root cause, execution path analysis, and applied fixes, adding them to a knowledge base for future reference.

Related Skills

Explore More Software Engineering Skills→
Ilenburg1993Ilenburg1993
3

reactive-bug-audit

Analyze stack traces and logs to identify root causes and apply minimal patches.

Community
Intermediate
oliver-kriskaoliver-kriska
517

phx:learn

Records bug-fix patterns and lessons learned into a central file.

Community
Basic
pckienuitpckienuit

systematic-debugging

Diagnose complex software bugs through reproduction, isolation, and root cause analysis.

Community
Intermediate
openaeonopenaeon
87

systematic-debugging

Investigate software bugs through a four-phase root-cause workflow with evidence gathering.

Community
Intermediate