skills.rest
lucasreydman
lucasreydmanCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

systematic-debugging

Enforce a four-phase root-cause debugging workflow before applying fixes.

Updated Mar 23, 2026
Search Tags:#testing#debugging#defense-in-depth#phases#root-cause#software-engineering
One-click install
npx skills add https://github.com/lucasreydman/lloyd --skill systematic-debugging-lucasreydman
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/lucasreydman/lloyd/tree/main/skills/superpowers/skills/systematic-debugging
Command: npx skills add https://github.com/lucasreydman/lloyd --skill systematic-debugging-lucasreydman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematically debugging bugs to identify root causes before applying fixes.

Core Features & Use Cases

  • Enforces a four-phase workflow: Root Cause Investigation, Pattern Analysis, Hypothesis and Testing, and Implementation.
  • Prevents symptom-focused fixes through explicit no fixes without root cause rule and anti-patterns.
  • Provides defense-in-depth patterns to catch regressions and ensure robust fixes.

Quick Start

Follow the four-phase systematic debugging process from Phase 1 to Phase 4, completing root-cause investigation before proposing fixes.

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 bug before applying a fix?▼

Root cause debugging requires completing a strict four-phase workflow: Root Cause Investigation, Pattern Analysis, Hypothesis and Testing, and Implementation. This enforces an explicit no-fixes-without-root-cause rule before applying any code changes.

What is the best way to stop fixing symptoms instead of the actual root cause?▼

To stop fixing symptoms, enforce a systematic debugging process with an explicit no-fixes-without-root-cause rule. This prevents symptom-focused patches by requiring pattern analysis and hypothesis testing before implementation.

Does systematic debugging work for both production bugs and integration tests?▼

Yes, systematic debugging applies to any technical issue across software projects, including production bugs, integration problems, and testing failures. It enforces a consistent root-cause investigation process regardless of the bug source.

How do I prevent regressions when implementing a bug fix?▼

To prevent regressions when implementing a bug fix, apply defense-in-depth practices alongside the root cause fix. This ensures robust implementation and catches future regressions across the software project.

What are the steps in a systematic root-cause debugging process?▼

The systematic root-cause debugging process consists of four phases: Phase 1 is Root Cause Investigation, Phase 2 is Pattern Analysis, Phase 3 is Hypothesis and Testing, and Phase 4 is Implementation of the verified fix.

Related Skills

Explore More Software Engineering Skills→
AgentientAgentient
2

SKILL_NAME_PLACEHOLDER

Centralize and trace full-stack errors with Sentry integration.

Official
Advanced
KanakMalpaniKanakMalpani

ai-regression-testing

Automate regression tests to detect AI-induced bugs in codebases.

Community
Advanced
LancerLabLancerLab

testing

Run unit tests and simulated sessions for GPU tuning scripts.

Official
Basic
outfitter-devoutfitter-dev
28

debugging-and-diagnosis

Enforce a four-phase root-cause investigation framework for software debugging.

Official
Advanced