Individual skill
reproduce-and-fix-issues
Reproduce a confirmed issue on the closest real surface, find root cause, and optionally prepare a minimal draft fix with evidence. Use after issue triage has enough information to attempt reproduction.
automations/benny/skills/reproduce-and-fix-issues/SKILL.md
Source commit 79595c97d47b5400034fb985e67f1a00389a81af
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 22
- Repository last updated
- Nov 1, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- ai-agents Repository topic
- claude-code Repository topic
- codex Repository topic
- coding-agents Repository topic
- cursor Repository topic
- pstack Repository topic
- cline Repository topic
- copilot Repository topic
- gemini Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# Reproduce and fix issues
1. Work in an isolated branch/worktree/sandbox when the host can provide one.
2. Reproduce the exact reported behavior and save the smallest durable evidence.
3. If reproduction fails, vary only evidence-backed environment assumptions; return the blocker instead of guessing.
4. Trace root cause. If a cheap behavioral regression test exists, see it fail for the same reason.
5. Make the smallest fix that explains the reproduction, then rerun the reproduction and targeted checks.
6. Prepare a draft change/PR only when authorized. Post status back to the source thread/ticket with proof and remaining uncertainty.