bug reproduction root cause hunter
- Repo stars 1
- Author repo claude-skills
- Domain
- Engineering
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 88 / 100 · heuristic scan, not runtime safety proof
- Runtime evidence
- Not run; no isolated runtime test evidence is currently recorded
- Author / version / license
- @00PrabalK00 · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No explicit requirements detected
- Detected file/system behavior
-
- Read-only
- Network behavior
- Local-only
- Install commands
- None (reference only)
Heads up: Tool permissions are not declared; actual access depends on the runtime.
# Bug Reproduction Root Cause Hunter
## Overview
Turn loose bug reports into a repeatable debugging workflow with evidence at each step.
## Core Workflow
1. Normalize the report. Capture expected behavior, actual behavior, exact errors, inputs, and environment details.
2. Reproduce the failure. Use existing tests, app commands, logs, or a minimal repro path before theorizing.
3. Narrow the surface. Identify the smallest set of files, conditions, flags, data states, or requests needed to trigger the bug.
4. Test hypotheses. Inspect recent diffs, surrounding code, and related tests to validate likely causes.
5. Propose the fix path. Recommend the smallest safe change, the regression test to add, and any rollout concerns.
## Deliver
- Provide exact repro steps when reproduction succeeds.
- State the most likely root cause with concrete evidence.
- If reproduction fails, document what was tried, what remains plausible, and the next best experiment.
- Keep the fix plan separate from the diagnosis.
## Guardrails
- Do not claim certainty without evidence.
- Prefer recent changes and environment differences as early suspects, not automatic conclusions.
- Preserve any raw error output needed to debug further.
Sections and files
Listed in source order.
sections -> Overview → Core Workflow → Deliver → Guardrails
terms -> Turn loose bug reports into a repeatable debugging workflow with evidence at each step. · 1. Normalize the report. · - Provide exact repro steps when reproduction succeeds. · - Do not claim certainty without evidence.
files/cmd -> no explicit files or commands
body sha256 -> b7bb8ca9d367
Overview
Turn loose bug reports into a repeatable debugging workflow with evidence at each step.
Core Workflow
Normalize the report. Capture expected behavior, actual behavior, exact errors, inputs, and environment details. Reproduce the failure. Use existing tests, app commands, logs, or a minimal repro path before theorizing. Narrow the surface. Identify the smallest set of files, conditions, flags, data states, or requests needed to trigger the bug. Test hypotheses. Inspect recent diffs, surrounding code, and related tests to validate likely causes.
Deliver
Provide exact repro steps when reproduction succeeds. State the most likely root cause with concrete evidence. If reproduction fails, document what was tried, what remains plausible, and the next best experiment. Keep the fix plan separate from the diagnosis.
Guardrails
Do not claim certainty without evidence. Prefer recent changes and environment differences as early suspects, not automatic conclusions. Preserve any raw error output needed to debug further.