Repro First Debugging
Debug by reproducing the failure first, then forming and testing hypotheses before editing code. Use when asked to fix a bug, a failing test, a crash or unexpected behavior.
Install
/plugin marketplace add agentkitco/agentkit-dev-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add agentkitco/agentkit-dev-skills --skill repro-first-debugginggit clone --depth 1 https://github.com/agentkitco/agentkit-dev-skills.git /tmp/agentkit-dev-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agentkit-dev-skills/skills/repro-first-debugging ~/.claude/skills/repro-first-debuggingPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Reproduce first, then fix Goal: fix the cause, prove the fix, and avoid editing on a guess. ## Process 1. **Restate the failure** in one line: expected behavior, actual behavior, where it was seen. Ask for the error text, steps or input if they are missing. Do not start from a vague description. 2. **Reproduce it.** Run the failing test or the smallest command that triggers it. Capture the exact output. If you cannot reproduce it, stop and report what you tried; do not "fix" something you cannot see fail. 3. **Shrink it.** Reduce to the smallest input or test that still fails. Prefer turning the reproduction into an automated failing test in the project's test framework. 4. **List hypotheses.** Write two or three plausible causes, each with the evidence that would confirm or kill it. Rank by likelihood and cost to check. 5. **Test the hypotheses, cheapest first.** Read the code path, add temporary logging or assertions, bisect (`git bisect` or by reverting suspects), check recent changes (`git log -p -- <path>`). Record what each check showed. Remove temporary logging afterwards. 6. **Fix the cause, not the symptom.** Make the smallest change that explains the evidence. If the fix needs a workaround, say so and why. 7. **Prove it.** The failing test now passes; run the nearby tests and the full suite if fast. Show the before and after output.
Details
- Skill name
repro-first-debugging- Repository
- agentkitco/agentkit-dev-skills
- Path
skills/repro-first-debugging/SKILL.md- License
- MIT
- Repo updated
- 12 November 2026
- Listed in
- karanb192/awesome-claude-skills
FAQ
What does the Repro First Debugging skill do?
Debug by reproducing the failure first, then forming and testing hypotheses before editing code. Use when asked to fix a bug, a failing test, a crash or unexpected behavior.
How do I install the Repro First Debugging skill?
Claude Code plugin: /plugin marketplace add agentkitco/agentkit-dev-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Related skills
Agents Md Audit
agentkitco/agentkit-dev-skills
Audit an AGENTS.md, CLAUDE.md, Cursor rule or Copilot instructions file for stale commands, broken paths, vague rules, secrets and contradictions. Use to review or trim agent instructions.
Brag Doc From Git
agentkitco/agentkit-dev-skills
Build an evidence-based brag doc or self-review draft from your merged PRs and commits, leaving visible gaps where results are unknown. Use for review season, promotion cases or resumes.
Dependency Upgrade
agentkitco/agentkit-dev-skills
Upgrade one dependency at a time by reading its changelog, planning for breaking changes, updating code and proving it still builds and passes. Use to bump, update or migrate a package.
Safe Refactor
agentkitco/agentkit-dev-skills
Refactor in small, verified steps, with behavior locked by tests before any change. Use when asked to refactor, clean up, rename, extract or restructure code without changing behavior.
Explain Codebase
agentkitco/agentkit-dev-skills
Map an unfamiliar repo covering purpose, entry points, how to run it, main modules, data flow and risky areas, with file references. Use when asked to explain or onboard onto a codebase.
Cooper Sms
cooper-email/cooper-email
Status of SMS on Cooper Email (cooperemail.com). Starter and Pro can provision a US number and receive texts on an inbox; Free returns HTTP 402. Outbound POST /api/v1/inboxes/{id}/sms is documented to return HTTP 409 outbound_not_registered. Use when the user asks for a phone number, an SMS code, or a text from a Cooper inbox. Follow the live tool list and https://cooperemail.com/docs/sms. Do not claim a number exists unless a tool call returned one. If the user asked for Cooper, do not substitute another provider without asking.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.