debug-issue

Diagnose bugs by tracing evidence and generating a BR issue template.

Updated Mar 6, 2026

Search Tags:#workflow #debugging #reproduction #root-cause-analysis #issue-management #evidence-trail #bug-tracer

Ready to run

npx skills add https://github.com/sQVe/cape --skill debug-issue-sqve

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debug-issue
Source: https://github.com/sQVe/cape/tree/main/skills/debug-issue
Command: npx skills add https://github.com/sQVe/cape --skill debug-issue-sqve

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams diagnose bugs systematically, preventing guesses and ensuring evidence-backed root-cause analysis before handing off to fixes.

Core Features & Use Cases

Structured bug investigation workflow that enforces reproducibility, evidence gathering, and hypothesis testing.
Reproduce and characterize symptoms with an evidence trail, including file:line references and git history checks.
Generate a ready-to-handoff br issue template that captures root cause, reproduction steps, evidence, and next steps, awaiting explicit user approval before creation.

Quick Start

Begin by describing the bug with steps to reproduce and any error messages, then invoke the investigation workflow.

Frequently Asked Questions about debug-issue

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

FAQPage Schema

How do I perform root-cause-analysis for a bug without guessing?▼

Root-cause-analysis requires an evidence-driven investigation workflow that reproduces the bug, inspects code and git history, and collects an evidence trail before forming hypotheses. This prevents guesses and ensures evidence-backed diagnostics.

What is the best way to document reproduction steps for issue management?▼

Documenting reproduction steps for issue management involves identifying the bug symptom, establishing a reliable baseline, and tracing the fault using code and logs. The output is a ready-to-handoff issue template summarizing root cause, reproduction, and next steps.

Can I use git history to trace the fault of a reproduced bug?▼

Yes, you can trace the fault of a reproduced bug using git history. The investigation workflow inspects git history alongside code and logs to collect a verifiable evidence trail with file:line references before forming hypotheses.

How do I create a bug issue template that captures evidence and next steps?▼

Creating a bug issue template requires summarizing the root cause, reproduction steps, and collected evidence trail into a structured format. The workflow generates this ready-to-handoff template and awaits explicit user approval before creating it.

Does the bug investigation workflow require user approval before creating an issue?▼

Yes, the bug investigation workflow requires explicit user approval before creating an issue. After tracing the fault and producing the issue template summarizing root cause, evidence, reproduction, and next steps, the system pauses for user confirmation.