Diagnose bugs by tracing evidence and generating a BR issue template.
npx skills add https://github.com/sQVe/cape --skill debug-issue-sqve
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
This skill helps teams diagnose bugs systematically, preventing guesses and ensuring evidence-backed root-cause analysis before handing off to fixes.
Begin by describing the bug with steps to reproduce and any error messages, then invoke the investigation workflow.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
gaebalaiAnalyze error logs and Git history to generate bug hypotheses and troubleshooting plans.
Hyeonjun0527Analyze logs, traces, and in-session state to diagnose OMC/Claude-Code session problems.
liauw-mediaTrace backward through call chains to identify original software fault triggers.
JansenAnalyticsMonitor application logs and stderr to detect errors, crashes, and exceptions.
