debug

Diagnose and resolve failing tests and gate checks through structured debugging phases.

6|Updated Mar 19, 2026

Search Tags:#testing #tdd #debugging #reproduce #root-cause #hypothesis-testing #gate-check

Ready to run

npx skills add https://github.com/nesquikm/dev-process-toolkit --skill debug-nesquikm

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/nesquikm/dev-process-toolkit/tree/main/plugins/dev-process-toolkit/skills/debug
Command: npx skills add https://github.com/nesquikm/dev-process-toolkit --skill debug-nesquikm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a disciplined, phase-driven approach to diagnosing and fixing failing tests, gate checks, or unexpected behavior.

Core Features & Use Cases

Phase-driven debugging: Root Cause Investigation, Pattern Analysis, Hypothesis Testing, and Implementation.
Repro & read: ensure you can reproduce, read failing code and changes, and verify fixes.
Guardrails: emphasizes safe, incremental fixes and rollback when needed.

Quick Start

Investigate and fix a failing gate check or test by following the four phases with the provided arguments.

Frequently Asked Questions about debug

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

FAQPage Schema

How do I debug a failing CI pipeline gate check using a structured workflow?▼

To debug a failing gate check, follow a structured debugging workflow with four phases: Root Cause Investigation, Pattern Analysis, Hypothesis Testing, and Implementation. This enforces reproducible steps and incremental fixes to prevent regression.

What is the best way to identify the root cause of unexpected behavior in local development?▼

Identifying a root cause requires methodical investigation where you first reproduce the error, read the failing code, and analyze patterns before testing hypotheses. This structured approach ensures you resolve the actual failure rather than just treating symptoms.

How do I apply hypothesis testing to fix failing tests without causing regressions?▼

Apply hypothesis testing by making controlled, incremental changes and verifying each fix against the failing test. This phase-driven approach emphasizes safe implementation and rollback capabilities to ensure new changes do not introduce further regressions.

Does this structured debugging protocol work for pre-release checks and local environments?▼

Yes, this structured debugging protocol applies to local development, CI pipelines, and pre-release checks. It diagnoses unexpected behavior and gate check failures across these environments by enforcing root-cause analysis and reproducible steps.

Why should I use a phase-driven debugging approach instead of directly patching failing code?▼

A phase-driven debugging approach prevents regression by enforcing root-cause analysis and change-by-change testing before implementation. Directly patching code often masks the underlying issue, whereas this methodical workflow ensures safe, incremental fixes with rollback options.