cmd-testing-debug

Guide root-cause investigation to diagnose software bugs before applying fixes.

2|Updated Jan 3, 2026
One-click install
npx skills add https://github.com/jlaws/dotfiles --skill cmd-testing-debug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cmd-testing-debug
Source: https://github.com/jlaws/dotfiles/tree/main/.agents/skills/cmd-testing-debug
Command: npx skills add https://github.com/jlaws/dotfiles --skill cmd-testing-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides developers through a disciplined root-cause investigation to diagnose bugs before attempting fixes, reducing wasted effort and repeated failures.

Core Features & Use Cases

  • Structured four-phase approach (Phase 1-4) for root-cause analysis and evidence gathering.
  • The Iron Law and Two-Attempt Rule to enforce disciplined debugging and prevent random fixes.
  • Step-by-step guidelines for error tracing, data flow analysis, and validation prior to changes.

Quick Start

Begin by collecting the failure context, then follow the four phases to identify the root cause before attempting any fix.

Frequently Asked Questions about cmd-testing-debug

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

FAQPage Schema
How do I find the root cause of intermittent test failures?

To find the root cause of intermittent test failures, follow a structured four-phase investigation approach that enforces evidence collection and data flow analysis before attempting fixes.

What is the best way to debug unexpected runtime behavior across a codebase?

The best way to debug unexpected runtime behavior is to apply disciplined root-cause analysis, tracing errors and validating evidence before implementing code changes.

How do I stop wasting effort on random fixes when troubleshooting software bugs?

To stop wasting effort on random fixes when troubleshooting software bugs, apply the Iron Law and Two-Attempt Rule, which enforce structured analysis and prevent undisciplined patching.

Can I use this systematic debugging method for diagnosing failing tests?

Yes, you can use this systematic debugging method for diagnosing failing tests, as it specifically scopes intermittent failures and unexpected runtime behavior into its root-cause investigation.

What steps should I follow for root-cause analysis before changing code?

For root-cause analysis before changing code, collect the failure context, follow the four phases to identify the root cause, and validate your findings prior to implementing any fixes.

Why should I gather evidence before applying fixes to software bugs?

You should gather evidence before applying fixes to software bugs because disciplined root-cause investigation reduces wasted effort and repeated failures caused by patching symptoms.