skills.rest
learnzdevelopmenthub
learnzdevelopmenthubCOMMUNITY
Explore all skills by this author →
GitHub

dev-debug

Reproduce failing tests, isolate faulty files, and document fix hypotheses.

1|Updated Apr 7, 2026
Search Tags:#git#testing#debugging#documentation#hypothesis#reproduction
One-click install
npx skills add https://github.com/learnzdevelopmenthub/paadhai --skill dev-debug-learnzdevelopmenthub
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev-debug
Source: https://github.com/learnzdevelopmenthub/paadhai/tree/main/.claude/skills/dev-debug
Command: npx skills add https://github.com/learnzdevelopmenthub/paadhai --skill dev-debug-learnzdevelopmenthub

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill imposes a reliable debug workflow when failures keep resurfacing so every reproduction, isolation, hypothesis, and verification step is guided and recorded.

Core Features & Use Cases

  • Phased reproduction: Reproduce failing commands with the stack test or user input while capturing exit codes and stack traces so no fix is proposed prematurely.
  • Isolation & hypothesis: Narrow down files, lines, triggers, and regressions before generating ranked hypotheses with predicted fixes and risks for user approval.
  • Verification to escalation: Execute the suspected fix, rerun commands, handle repeated failures with architectural escalation, document results in docs/plans/issue-<n>/debug.md, and summarize next steps for /dev-pr or /dev-implement.

Quick Start

Ask the dev-debug skill to reproduce the failure, isolate the cause, and document the chosen hypothesis and verification results.

Frequently Asked Questions about dev-debug

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

FAQPage Schema
How do I systematically debug failing tests and isolate the faulty code?▼

Systematic debugging reproduces failing commands to capture exit codes and stack traces, narrows down faulty files, and generates ranked hypotheses with predicted fixes before applying changes.

What is the best way to reproduce a failing test before proposing a code fix?▼

The best way to reproduce a failing test is by executing stack test commands or user inputs to capture exact stack traces and exit codes, ensuring no fix is proposed prematurely.

How do I document a debugging workflow for a production hotfix?▼

Document a production hotfix workflow by recording reproduction, isolation, hypothesis, and verification outcomes in docs/plans/issue-<n>/debug.md to maintain a reliable investigation trail.

Can I use a phased debugging workflow for feature branch regressions?▼

Yes, a phased debugging workflow applies to feature branch regressions by isolating triggers and regressions, verifying the suspected fix, and escalating repeated failures architecturally.

Why do my code fixes keep resurfacing when debugging failing tests?▼

Code fixes keep resurfacing because of unsystematic debugging, which this Skill prevents by guiding you through phased reproduction, isolation, ranked hypothesis generation, and strict verification.

Related Skills

Explore More Software Engineering Skills→
vadimcomanescuvadimcomanescu
24

error-resolver

Diagnose software and runtime errors to identify root causes.

Community
Advanced
glowingkittyglowingkitty
43

openmates:pullrequest

Create GitHub pull requests from dev to main with categorized commit descriptions.

Community
Intermediate
louisfghbvclouisfghbvc
4

investigate

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

Community
Advanced
freedomw1987freedomw1987
2

node-inspect-debugger

Debug Node.js applications via the V8 inspector and Chrome DevTools Protocol.

Community
Intermediate