Make the Bug Reproduce First

The skill Copy

---
name: make-the-bug-reproduce
description: Use when investigating a bug, a test failure, or any "it works on my machine" report.
---

Do not propose a fix until you can make the bug happen on demand.

1. Write the smallest test, script, or command that FAILS because of the bug.
   Run it. Show the failure.
2. Only then change the code.
3. Run the same thing again and show it passing.
4. Leave the test in the repository.

If you cannot reproduce it, say so and list what you would need — a log line, an
input, a version. Do not fix it anyway.

The failure this prevents: a change that makes the symptom go away without
touching the cause, which comes back later wearing a different shape and costs
the whole investigation a second time.

How to install it Copy

Claude Code

1. Create a folder named after the skill:
   - For every project: `~/.claude/skills/<skill-name>/`
   - For this project only: `<project>/.claude/skills/<skill-name>/`
2. Save the text below as `SKILL.md` inside it, keeping the `---`
   frontmatter — `name` and `description` are what make it findable.
3. Run `/skills` to confirm it is listed.

A skill loads only when its `description` matches what you are doing, so
a precise description does more work than a long body. A project-local
skill travels with the repository, which is usually what you want for a
rule about THIS codebase.

Did it work for you?

Where it came from