debug-issue

Orchestrate six-phase debugging workflows from reproduction to verification.

9|1|Updated Jan 8, 2026

Search Tags:#investigation #verification #debug #root-cause #reproduction #git-workflow #failing-test

Ready to run

npx skills add https://github.com/conn-castle/agent-layer --skill debug-issue-conn-castle

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debug-issue
Source: https://github.com/conn-castle/agent-layer/tree/main/internal/templates/skills/debug-issue
Command: npx skills add https://github.com/conn-castle/agent-layer --skill debug-issue-conn-castle

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured, investigation-first debugging workflow that guides teams from symptom to root cause, reproducible evidence, failing tests, fixes, and verification.

Core Features & Use Cases

Structured six-phase investigation workflow including preflight, reproduction, narrowing, diagnosis, failing test generation, fix implementation, and verification.
Recommended multi-agent roles (Repo scout, Reproducer, Investigator, Test writer, Fixer, Verifier) to coordinate debugging work.
Guardrails and artifacts ensure reproducibility and traceability, e.g., run-id based reports and logging to ISSUES.md for tracking.

Quick Start

Describe the symptom to initiate Phase 1 and follow Phases 1 through 6 to reproduce, narrow the cause, diagnose, write a failing test, implement a fix, and verify the result.

Frequently Asked Questions about debug-issue

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

FAQPage Schema

How do I debug a software defect from symptom to root cause?▼

Root cause analysis for failing tests involves reproducing the error, narrowing the codebase scope, diagnosing the underlying fault, and generating a failing test case to validate the fix before final verification.

What is the best way to reproduce a bug and track the investigation?▼

To investigate bugs fast, initiate a preflight phase by describing the symptom, then execute phases for reproduction, narrowing, diagnosis, failing test generation, fix implementation, and final verification.

Can I coordinate a multi-agent team for codebase investigation and verification?▼

Yes, debugging codebases without a structured workflow often leads to incomplete root cause analysis; enforcing a six-phase protocol with artifacts like run-id reports and ISSUES.md ensures reproducible evidence and traceable fixes.

Does a structured debugging workflow support git-workflow integration for fixing tests?▼

A structured debugging workflow generates artifacts like run-id based reports for tracking investigations and logs issues to ISSUES.md, ensuring every reproduction, diagnosis, and fix is traceable and verifiable.