skills.rest
rapyuta-robotics
rapyuta-roboticsOFFICIAL
Explore all skills by this author →
WebsiteGitHub

systematic-debugging

Diagnose root causes of bugs through a four-phase investigation process.

Updated Aug 23, 2026
Search Tags:#debugging#defense-in-depth#software-quality#root-cause-analysis#phase-based#systematic-debugging
One-click install
npx skills add https://github.com/rapyuta-robotics/agent-ai --skill systematic-debugging-rapyuta-robotics
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/rapyuta-robotics/agent-ai/tree/main/skills/systematic-debugging
Command: npx skills add https://github.com/rapyuta-robotics/agent-ai --skill systematic-debugging-rapyuta-robotics

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill guides engineers to diagnose the underlying causes of bugs, failures, or unexpected behavior before proposing or implementing any fixes.

Core Features & Use Cases

  • Phase-driven process: Enforces a four-phase workflow (Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, Implementation) to ensure evidence-based resolutions.
  • Evidence gathering: Provides structured guidelines for reproducing issues, collecting logs, and tracing data flow across components.
  • Defense-in-depth mindset: Encourages validating fixes across multiple layers to prevent regressions and reoccurring faults.
  • Use Case Example: When a production bug surfaces, follow the process to isolate root cause and implement a robust, well-vetted solution rather than a quick patch.

Quick Start

Use the four-phase process to analyze a failing scenario: Phase 1, Phase 2, Phase 3, Phase 4, and verify with tests.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema
What is systematic debugging and when do I need it for production bugs?▼

Systematic debugging is a phase-based process to find the root cause of bugs before fixing them. You need it for production bugs, test failures, or performance issues to avoid guesswork and prevent regressions.

How do I find the root cause of a bug instead of just patching it?▼

To find the root cause of a bug, follow a four-phase process: Root Cause Investigation, Pattern Analysis, Hypothesis and Testing, and Implementation. This enforces evidence gathering and reproduces issues before applying fixes.

What's the best way to debug test failures across complex software components?▼

The best way to debug test failures is using a defense-in-depth approach that traces data flow across components, collects logs, and validates fixes across multiple layers to prevent recurring faults.

Does this debugging process work for any technical issue or only specific platforms?▼

This debugging process works for any technical issue across software projects, including test failures, production bugs, and performance problems, without relying on specific platforms or external dependencies.

How to validate a bug fix and prevent regressions before implementation?▼

To validate a bug fix and prevent regressions, apply a defense-in-depth mindset during the Implementation phase, verifying the solution across multiple layers and confirming the fix with tests.

Related Skills

Explore More Software Engineering Skills→
yuridefrancayuridefranca

root-cause-analyzer

Reproduce bugs and trace state flows to produce evidence-backed root cause reports.

Community
Advanced
Productfculty-aipmProductfculty-aipm
70

improvement-flywheel

Design a continuous improvement flywheel for AI product quality.

Community
Advanced
automagik-devautomagik-dev
328

report

Investigate bugs and create GitHub issues from code analysis, browser evidence, and observability data.

Official
Advanced
darthlinuxerdarthlinuxer

systematic-debugging

Reproduce, isolate, analyze, and verify software defects with root cause analysis.

Community
Intermediate