skills.rest
jerelvelarde
jerelvelardeCOMMUNITY
Explore all skills by this author →
GitHub

debug-systematic

Automate a four-phase debugging workflow to reproduce, isolate, root-cause, and verify fixes.

6|Updated Feb 19, 2026
Search Tags:#workflow#debugging#troubleshooting#verify#reproduce#root-cause#isolate
One-click install
npx skills add https://github.com/jerelvelarde/chalk-skills --skill debug-systematic-jerelvelarde
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug-systematic
Source: https://github.com/jerelvelarde/chalk-skills/tree/main/skills/debug-systematic
Command: npx skills add https://github.com/jerelvelarde/chalk-skills --skill debug-systematic-jerelvelarde

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a disciplined, four-phase debugging workflow to systematically identify root causes rather than chasing symptoms.

Core Features & Use Cases

  • Reproduce: capture exact conditions and environment to validate the bug.
  • Isolate & Root-cause: narrow down the failing component and identify the underlying cause with guided reasoning.
  • Verify: confirm the fix through regression checks and clear criteria, reducing risk of regressions.
  • Use Case: teams debugging flaky or intermittent bugs across codebases and environments.

Quick Start

Provide a bug report and context, then trigger the four-phase debugging workflow to reproduce, isolate, root-cause, and verify the fix.

Frequently Asked Questions about debug-systematic

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

FAQPage Schema
What is a systematic debugging workflow for finding software bug root causes?▼

A systematic debugging workflow enforces an explicit sequence—Reproduce, Isolate, Root-cause, and Verify—to identify underlying causes rather than chasing symptoms. It captures exact conditions to validate the bug before narrowing down the failing component.

How do I debug intermittent or flaky bugs across different environments?▼

To debug flaky bugs across environments, start by reproducing the exact conditions and environment to validate the bug. Then isolate the failing component, identify the root cause through guided reasoning, and verify the fix with regression checks.

Can I use this debugging workflow for any software project or codebase?▼

Yes, this debugging workflow applies to software debugging, bug investigations, and troubleshooting across projects and environments. It requires no specific dependencies or components, making it adaptable to any codebase.

What's the best way to verify a software fix and prevent regressions?▼

The best way to verify a fix and prevent regressions is to apply explicit exit criteria during the Verify phase. Confirm the fix through regression checks and clear criteria to ensure the original bug is resolved without introducing new issues.

Why should I isolate a failing component before applying a bug fix?▼

Isolating a failing component before applying a fix ensures you address the actual defect rather than a secondary symptom. This phase narrows down the problematic code area, enabling precise root-cause identification through guided reasoning.

Related Skills

Explore More Software Engineering Skills→
cslsoftwarescslsoftwares

quality-bug-triage

Convert informal bug reports into structured tickets with severity and reproduction steps.

Community
Intermediate
rakhnianskii9rakhnianskii9

regression-suite

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

Community
Advanced
krzemienskikrzemienski
2

cli-validation

Validate CLI binaries and capture stdout, stderr, and exit codes.

Community
Intermediate
idealic-aiidealic-ai

chores

Automate routine maintenance and cleanup tasks from a structured task queue.

Official
Advanced