skills.rest
capaas2
capaas2COMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Diagnose software failures through structured reproduction, isolation, and root cause analysis.

Updated Apr 4, 2026
Search Tags:#debugging#troubleshooting#root cause analysis#verification#reproduction
One-click install
npx skills add https://github.com/capaas2/Site-teste --skill systematic-debugging-capaas2
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/capaas2/Site-teste/tree/main/.agent/skills/systematic-debugging
Command: npx skills add https://github.com/capaas2/Site-teste --skill systematic-debugging-capaas2

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you debug complex issues without guessing by forcing a reproducible, evidence-based process that leads to the true root cause.

Core Features & Use Cases

  • Reproduce and isolate issues: Capture exact steps, determine frequency, and narrow the problem to the smallest triggering change.
  • Root cause analysis: Use structured questioning and the 5 Whys to move beyond symptoms and identify why the failure is happening.
  • Fix and verify: Confirm the issue is resolved, preserve related functionality, and add regression tests to prevent recurrence.

Quick Start

Use the systematic-debugging skill to analyze this bug, reproduce it, isolate the cause, and verify a safe 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 a complex software failure?▼

Root cause analysis finds the true origin of a complex software failure by turning vague symptoms into reproducible evidence. It uses structured questioning like the 5 Whys to move past symptoms and pinpoint the exact triggering change.

What is the best way to reproduce and isolate an intermittent bug?▼

Reproducing and isolating an intermittent bug requires capturing exact triggering steps and determining the failure frequency to narrow the problem down to the smallest possible environmental or code change.

How do I verify a bug fix without breaking existing functionality?▼

Verifying a bug fix safely involves confirming the original issue is resolved, checking that related functionality remains intact, and adding regression tests to prevent the same failure from recurring in the future.

Can I use systematic debugging for issues across code, logs, and environment-specific behavior?▼

Systematic debugging applies to diagnosing complex failures across code, logs, recent changes, and environment-specific behavior by enforcing a structured process of reproduction, isolation, and evidence-based analysis.

Why does my troubleshooting process keep addressing symptoms instead of the true cause?▼

Troubleshooting often addresses symptoms instead of the true cause when it lacks a reproducible, evidence-based process, which this approach solves by forcing structured isolation and root cause analysis.

Related Skills

Explore More Software Engineering Skills→
geoffreywoogeoffreywoo

investigate

Guide systematic debugging by collecting symptoms and inspecting code to identify root causes.

Community
Advanced
aist-ai-sastaist-ai-sast

mcp-regression-fix

Diagnose MCP regression failures and implement durable fixes across test suites.

Official
Advanced
MinhmiceMinhmice

debugger

Investigate software defects and regressions using logs, traces, and diffs.

Community
Advanced
cegit27cegit27
3

canary

Monitor live production apps for console errors and performance regressions.

Official
Advanced