skills.rest
DVNghiem
DVNghiemCOMMUNITY
Explore all skills by this author →
GitHub

debug-flow

Diagnose software bugs through a systematic debugging workflow and structured Debug Report.

20|3|Updated Apr 30, 2026
Search Tags:#testing#debugging#root-cause#bisect#reproduction#bug-fix#stack-trace
One-click install
npx skills add https://github.com/DVNghiem/FlowDeck --skill debug-flow
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug-flow
Source: https://github.com/DVNghiem/FlowDeck/tree/main/src/skills/debug-flow
Command: npx skills add https://github.com/DVNghiem/FlowDeck --skill debug-flow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging workflow that helps engineers reproduce issues, isolate root causes, write failing tests, and verify fixes.

Core Features & Use Cases

  • Guided reproduction: Reproduce bugs reliably from reports or failing tests.
  • Root-cause analysis: Trace errors from top to origin and identify invariants violations.
  • Bisect and validation: Use guided bisect strategies to locate regressions and validate fixes with tests.
  • Audit and documentation: Generate a Debug Report detailing root cause, evidence, call path, and test outcomes.

Quick Start

Describe the failing scenario and trigger the debugging flow to reproduce the issue and start the root-cause analysis.

Frequently Asked Questions about debug-flow

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

FAQPage Schema
How do I find the root cause of a software bug from a stack trace?▼

To find the root cause from a stack trace, trace errors from the top level to their origin, identify invariant violations, and isolate the exact failure point using a systematic debugging workflow.

What is the best way to locate a code regression without knowing which commit caused it?▼

The best way to locate a code regression is using a guided bisect strategy to systematically narrow down commits, validate the suspected change, and confirm the regression source with targeted tests.

How do I reliably reproduce a flaky test to debug the failure?▼

To reliably reproduce a flaky test, follow a guided reproduction workflow that analyzes the failing scenario and test reports to consistently trigger the issue and start isolating the root cause.

Can I use this debugging workflow for both production errors and failing tests?▼

Yes, you can use this debugging workflow for production errors and failing tests. It guides you through reproduction, trace analysis, failing-test creation, fix application, and verification for both scenarios.

How do I document a bug fix and verify the root cause resolution?▼

To document a bug fix and verify root cause resolution, generate a structured Debug Report detailing the root cause, evidence, call path, applied fix, and test outcomes to validate the resolution.

What is a disciplined debugging flow for isolating software bugs?▼

A disciplined debugging flow systematically guides engineers through bug reproduction, root-cause isolation, failing-test creation, fix application, and verification to diagnose and resolve software bugs end-to-end.

Related Skills

Explore More Software Engineering Skills→
jk278jk278

debugging-assistant

Diagnose software bugs from stack traces and error logs.

Community
Advanced
dfrysingerdfrysinger
36

implement

Execute test-driven development with failing tests, minimal implementation, and verified passing tests.

Community
Advanced
photoszztphotoszzt

tla-debug-violations

Debug TLA+ invariant and property violations reported by the TLC model checker.

Community
Advanced
zz8011zz8011

canary

Monitors deployed pages for console errors, performance issues, and page failures against baselines.

Community
Advanced