skills.rest
ceshez
ceshezCOMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

...

Updated Aug 27, 2026
Search Tags:#debugging#root cause#test failures#flaky tests#hypothesis testing#incident response#defense in depth
One-click install
npx skills add https://github.com/ceshez/VELAR --skill systematic-debugging-ceshez
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/ceshez/VELAR/tree/main/.agents/skills/systematic-debugging
Command: npx skills add https://github.com/ceshez/VELAR --skill systematic-debugging-ceshez

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

Prevents wasted time and repeated failures by forcing a disciplined process that always locates the real root cause before proposing any fixes.

Core Features & Use Cases

  • Root-cause-first debugging mandate: Prohibits proposing fixes until Phase 1 (Root Cause Investigation) is completed, using the iron law: NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST.
  • Pressure-resistant 4-phase workflow: Runs a complete Investigation → Pattern Analysis → Hypothesis & Testing → Implementation loop to confirm what is wrong and prove the fix.
  • Anti-flakiness and structural robustness tools: Includes supporting techniques like root-cause tracing, defense-in-depth validation, and condition-based waiting to avoid symptom masking and timing guesses.
  • Use cases: test failures, production bugs, unexpected behavior, performance issues, build failures, and integration problems—especially under time pressure or when “one quick fix” feels obvious.

Quick Start

Follow Phase 1 Root Cause Investigation by reading the error messages carefully, reproducing consistently, checking recent changes, gathering evidence across component boundaries, tracing the data flow backward, and only then moving to hypothesis and implementation.

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 changing code?▼

To find the root cause of a bug, you must complete an evidence-based investigation phase that reproduces the issue consistently and traces data flow across boundaries before proposing any fixes.

What is the best way to debug flaky tests and intermittent failures?▼

Debugging flaky tests requires condition-based waiting and defense-in-depth validation to avoid timing guesses, ensuring you trace the structural root cause rather than masking symptoms with quick fixes.

Why do my repeated fixes for test failures keep failing?▼

Repeated fixes fail because they address symptoms instead of root causes. You must stop applying patches, re-analyze the evidence, and enforce a strict root-cause investigation before making any further changes.

Does root cause debugging work for build failures and integration problems?▼

Yes, root cause debugging applies to build failures and integration problems. It enforces reading error messages carefully and gathering evidence across component boundaries before moving to hypothesis testing.

When should I stop trying quick fixes during incident response?▼

You should stop applying quick fixes during incident response when a fix fails. Explicit rules require you to halt and re-analyze the evidence to locate the real root cause before attempting another minimal change.

Related Skills

Explore More Software Engineering Skills→
scruffydanscruffydan

systematic-debugging

Identify root causes of software defects through a four-phase debugging workflow.

Community
Intermediate
dmae97dmae97
130

omk-flow-bugfix

Guide bug resolution from reproduction evidence to root-cause analysis and minimal code changes.

Community
Intermediate
obraobra
269.6k

systematic-debugging

Guide software debugging through a four-phase root cause investigation process.

Community
Intermediate
Likas07Likas07

systematic-debugging

Guide a 4-phase root cause investigation process for technical issues.

Community
Advanced