skills.rest
GeneralJerel
GeneralJerelCOMMUNITY
Explore all skills by this author →
GitHub

debug-systematic

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging workflows help teams avoid shotgun debugging by enforcing a structured approach to reproduce, isolate, root-cause, and verify fixes.

Core Features & Use Cases

  • Reproduce phase guidance: captures exact steps, environment, and inputs to reliably recreate the issue.
  • Isolate phase techniques: narrow down the failing subsystem using data flow tracing, logs, and targeted tests.
  • Root-Cause phase with 5 Whys: uncovers underlying causes and documents rationale for the fix.
  • Verify phase & regression readiness: provides checks and guidance to validate fixes with lightweight tests.

Quick Start

Describe the issue and let the four-phase workflow guide you from reproduction through verification.

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 software projects?▼

A systematic debugging workflow prevents shotgun debugging by enforcing a structured four-phase sequence: reproduce the issue, isolate the failing subsystem, root-cause the underlying defect, and verify the fix. This ensures traceable and reliable code fixes.

How do I isolate a bug in a failing software deployment?▼

To isolate a bug in a failing software deployment, narrow down the failing subsystem using data flow tracing, logs, and targeted tests. This isolation phase ensures you pinpoint the exact component before proceeding to root-cause analysis.

How do I find the root cause of a bug using the 5 Whys technique?▼

Find the root cause of a bug by applying the 5 Whys technique to iteratively ask why the issue occurs, uncovering underlying causes rather than surface symptoms. This process documents the rationale driving the fix.

Can I use this structured debugging workflow for services and integration issues?▼

Yes, you can use this structured debugging workflow for services and integration issues. It is designed for software projects, services, and environments where issues arise in code, deployments, or integrations.

What is the best way to reproduce a bug reliably before fixing it?▼

The best way to reproduce a bug reliably is to capture the exact steps, environment details, and inputs that trigger the issue. This reproduction phase provides the foundation for isolating the failing subsystem.

How do I verify a bug fix and prevent regressions in my code?▼

Verify a bug fix and prevent regressions by applying lightweight tests and checks during the verification phase. This validates that the fix resolves the issue and ensures regression readiness for future deployments.

Related Skills

Explore More Software Engineering Skills→
louisfghbvclouisfghbvc
4

investigate

Guide a debugging workflow to identify root causes of software defects.

Community
Advanced
robkamrobkam
12

bugfix-red-green-proof

Enforce a red-green-proof loop starting with a failing regression test.

Community
Advanced
aRustyDevaRustyDev

systematic-debugging

Investigate root causes before fixes using a four-phase debugging workflow.

Community
Advanced
keremtoker468-dotcomkeremtoker468-dotcom

systematic-debugging

Guide hypothesis-driven debugging through four phases for root cause analysis.

Community
Advanced