skills.rest
pckienuit
pckienuitCOMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

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

Updated Mar 30, 2026
Search Tags:#debugging#troubleshooting#root cause analysis#logging#verification#reproduction
One-click install
npx skills add https://github.com/pckienuit/GameDev1 --skill systematic-debugging-pckienuit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/pckienuit/GameDev1/tree/main/.cursor/skills/systematic-debugging
Command: npx skills add https://github.com/pckienuit/GameDev1 --skill systematic-debugging-pckienuit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you diagnose complex software issues without random guessing, so you can move from symptoms to a verified root cause.

Core Features & Use Cases

  • Reproduce First: Confirm the bug consistently before making changes.
  • Isolate the Failure: Narrow the problem with targeted questions, minimal test cases, and recent-change analysis.
  • Understand the Root Cause: Use structured root-cause analysis to explain why the issue happens, not just what it looks like.
  • Fix and Verify: Check that the repair works, preserves related behavior, and prevents regressions.
  • Use Case: Ideal for intermittent crashes, broken features after a refactor, unclear test failures, and production incidents that need evidence-based troubleshooting.

Quick Start

Use this skill to analyze the issue step by step, reproduce the bug, isolate the cause, explain the root cause, and verify the fix.

Frequently Asked Questions about systematic-debugging

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

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

To diagnose an unclear runtime error, systematically isolate the failure by analyzing recent code changes and gathering logs. Structured root cause analysis explains why the error happens so you can fix the underlying issue rather than just treating symptoms.

What is the best way to troubleshoot a regression after a code refactor?▼

Troubleshooting a regression involves confirming the bug's reproduction steps, isolating variables with targeted questions, and performing root cause analysis. This process ensures you understand why the refactor introduced the failure before applying and verifying a fix.

How do I verify a bug fix without introducing new regressions?▼

Verify a bug fix by checking that the repair resolves the original issue while preserving related behavior. Evidence-based troubleshooting requires confirming the initial reproduction case is fixed and testing for regressions to ensure system stability.

Can I use structured debugging for production incidents?▼

Yes, structured debugging applies to production incidents by requiring evidence gathering and reproduction of the failure. It helps diagnose complex runtime issues across environments by isolating the root cause before applying verified fixes.

Related Skills

Explore More Software Engineering Skills→
sQVesQVe

debug-issue

Diagnose bugs by tracing evidence and generating a BR issue template.

Community
Advanced
chriswesttchriswestt

gstack-openclaw-investigate

Identify bug root causes through symptom collection, code path tracing, and deterministic reproduction.

Community
Advanced
cosmixcosmix
53

debugging

Diagnose and resolve software bugs across programming languages and environments.

Community
Intermediate
florianhornerflorianhorner
4

canary

Monitor live web apps for console errors and page failures after deployment.

Community
Advanced