skills.rest
baekenough
baekenoughCOMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Enforce a seven-phase reproduce-first debugging workflow for software failures.

13|6|Updated Apr 14, 2026
Search Tags:#debugging#workflows#software-engineering#root-cause-analysis#test-failure#reproduce-first
One-click install
npx skills add https://github.com/baekenough/second-brain --skill systematic-debugging-baekenough
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/baekenough/second-brain/tree/main/.claude/skills/systematic-debugging
Command: npx skills add https://github.com/baekenough/second-brain --skill systematic-debugging-baekenough

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic-debugging provides a disciplined, reproduce-first debugging workflow to diagnose and fix bugs, reducing guesswork and speeding up root-cause resolution.

Core Features & Use Cases

  • Structured seven-phase workflow (Problem statement, Reproduction, Evidence, Root-cause Hypothesis, Failing Guard, One-Fix Implementation, and Verification) to guide every debugging session.
  • Templates and guardrails ensure consistent, auditable debugging across teams and projects.
  • Applicable to unit, integration, and system bugs, as well as runtime issues and flaky tests in development and CI.

Quick Start

Initiate the seven-phase debugging process on the failing issue, documenting each phase and linking artifacts to ensure a reproducible fix.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema
How do I systematically debug flaky tests and trace the root cause?▼

A structured debugging workflow enforces a reproduce-first, root-cause-first process using a seven-phase template to diagnose and fix flaky tests, preventing guesswork and ensuring consistent root-cause resolution.

What is the best way to establish a reproducible debugging workflow for CI failures?▼

A disciplined debugging workflow enforces reproduction-first steps and structured templates to establish reproducible processes for CI failures, ensuring auditable root-cause resolution across teams and projects.

Can I use this structured debugging workflow for both local development and CI environments?▼

Yes, this debugging workflow applies to software projects tracking down failures, flaky tests, or unexpected behavior across both local development and CI environments using structured templates and guardrails.

How do I create a failing test guard before fixing a software bug?▼

The debugging workflow includes a failing guard phase requiring you to write a failing test that reproduces the bug before implementing the single fix, ensuring the root cause is accurately captured and verified.

Why should I use a root-cause-first debugging workflow instead of trial-and-error fixes?▼

A root-cause-first debugging workflow reduces guesswork and speeds up resolution by enforcing evidence collection, root-cause hypothesis, and a failing guard before applying a single fix, ensuring verified resolution over trial-and-error.

Related Skills

Explore More Software Engineering Skills→
jlissnerjlissner

grimoire-bug

Reproduce reported bugs with failing tests before implementing minimal fixes.

Community
Intermediate
rakhnianskii9rakhnianskii9

regression-suite

Generate a regression test manifest and status reports from sprint plans and test inventories.

Community
Advanced
kennyolofsson23-netizenkennyolofsson23-netizen

kaizen:root-cause-tracing

Trace errors back through call chains to locate original triggers.

Community
Advanced
Mekann2904Mekann2904

log-analyzer

Analyze log files to extract error patterns and detect anomalies.

Community
Intermediate