skills.rest
mopeyjellyfish
mopeyjellyfishCOMMUNITY
Explore all skills by this author →
GitHub

debug

Reproduce bugs from evidence and prove root causes with red signals.

1|Updated Apr 18, 2026
Search Tags:#debug#evidence#root-cause#reproduction#incident-management#bug-investigation#causal-hypothesis
One-click install
npx skills add https://github.com/mopeyjellyfish/flywheel --skill debug-mopeyjellyfish
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/mopeyjellyfish/flywheel/tree/main/skills/debug
Command: npx skills add https://github.com/mopeyjellyfish/flywheel --skill debug-mopeyjellyfish

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Investigate and fix bugs from evidence, transforming ambiguous failures into a clear, verifiable causal path.

Core Features & Use Cases

  • Reproduce bugs from live evidence and stack traces
  • State causal hypotheses and prove them with red signals
  • Guide from incident to fix or escalation to design discussions

Quick Start

Provide a bug report and reproduction steps to start a structured debugging session.

Frequently Asked Questions about debug

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

FAQPage Schema
How do I prove the root cause of a bug from a stack trace?▼

You prove a bug root cause by reproducing the failure from live evidence and stating causal hypotheses. This structured debugging process transforms ambiguous stack traces into a clear, verifiable causal path.

What is the best way to investigate an incident using reproduction steps?▼

Incident investigation requires a structured debugging flow that captures reproduction steps and evidence. This approach proves causal hypotheses with red signals, guiding teams from ambiguous failures to safe fixes.

How do I structure bug investigation for failing tests?▼

You structure bug investigation for failing tests by applying a structured input flow to capture reproduction steps and evidence. This generates a red signal that proves the root cause and ensures a safe fix.

When do I need to escalate a bug investigation to design discussions?▼

You escalate a bug investigation to design discussions when the structured debugging process fails to prove a clear causal path from the evidence, preventing a safe and verifiable fix.

Can I use structured debugging to fix ambiguous failures without reproduction steps?▼

No, you cannot fix ambiguous failures without reproduction steps. The debugging process explicitly requires a structured input flow of reproduction steps, evidence, and causal hypotheses to generate a verifiable red signal.

Related Skills

Explore More Software Engineering Skills→
santosomarsantosomar
1

bug-localization

Localize the exact file, function, or line introducing a bug from stack traces, tests, logs, and reports.

Community
Advanced
lumenhelixsolutionslumenhelixsolutions
1

ce-debug

Identify software bug root causes and implement test-first verified fixes.

Community
Advanced
Eigo-Mt-FujiEigo-Mt-Fuji

bug-hunter

Guide structured bug investigation and root cause analysis with verification steps.

Community
Advanced
icartshicartsh
4

error-detective

Parse stack traces and guide error resolution with the TRACE framework.

Community
Advanced