skills.rest
byunghak-dable
byunghak-dableCOMMUNITY
Explore all skills by this author →
GitHub

work-debug

Identify root causes of bugs and test failures through evidence analysis.

Updated Sep 12, 2023
Search Tags:#code quality#testing#debugging#troubleshooting#root cause analysis#bug fixing
One-click install
npx skills add https://github.com/byunghak-dable/.dotfiles --skill work-debug
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: work-debug
Source: https://github.com/byunghak-dable/.dotfiles/tree/main/claude/.claude/skills/work-debug
Command: npx skills add https://github.com/byunghak-dable/.dotfiles --skill work-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps you systematically trace and fix the root cause of bugs and test failures, preventing superficial symptom fixes.

Core Features & Use Cases

  • Root Cause Analysis: Prioritizes identifying the fundamental cause of an issue before attempting a fix.
  • Evidence-Based Debugging: Gathers evidence through code analysis, commit history, and error logs.
  • Use Case: When a critical bug is reported in production, this Skill will guide you through analyzing the error message, examining recent code changes, and confirming the issue with the user to pinpoint the exact source of the problem.

Quick Start

Use the work-debug skill to debug the 'NullPointerException' occurring in the user authentication module.

Frequently Asked Questions about work-debug

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

FAQPage Schema
How do I systematically debug code issues instead of just fixing symptoms?▼

Systematically debug code issues by following a strict process of evidence collection, verification, pattern comparison, and hypothesis formulation to pinpoint the root cause before applying minimal modifications.

What is the best way to find the root cause of bugs and test failures?▼

Root cause analysis for bugs and test failures involves gathering evidence through error analysis, change tracking, and user confirmation to ensure fixes address the underlying problem rather than superficial symptoms.

How does evidence-based debugging work when troubleshooting a critical production bug?▼

Evidence-based debugging works by analyzing error messages, examining recent code changes via commit history, and verifying patterns to formulate a hypothesis, ensuring the fix targets the exact source of the problem.

Can I use this debugging approach for a NullPointerException in my authentication module?▼

Yes, you can debug a NullPointerException by analyzing the error, examining recent code changes, and confirming the issue with the user to pinpoint the exact source of the problem in the authentication module.

What are the limitations of systematic root cause analysis for bug fixing?▼

Systematic root cause analysis for bug fixing requires thorough evidence collection and user confirmation, which may delay immediate patching but prevents superficial symptom fixes and recurring issues.

Do I need any specific testing frameworks to perform root cause analysis on code issues?▼

No specific testing frameworks are required to perform root cause analysis. The process relies on analyzing error logs, tracking code changes, and verifying hypotheses through evidence collection and minimal modification.

Related Skills

Explore More Software Engineering Skills→
rnbenrnben

systematic-debugging

Diagnose bugs through a structured four-phase root-cause investigation.

Community
Advanced
dmae97dmae97
130

omk-flow-bugfix

Guide bug resolution from reproduction evidence to root-cause analysis and minimal code changes.

Community
Intermediate
heyallencaoheyallencao
118

ks-verify

Run automated test suites and coverage checks to validate code claims.

Community
Intermediate
wesleyosantos91wesleyosantos91
6

hotfix

Apply a minimal corrective patch with root-cause analysis and mandatory tests.

Community
Intermediate