Bug replay

Skill mustafa3252/vibe-ship-skills/skills/bug-replay

Practical agent skills for vibe coders: move fast, verify faster, ship cleaner.

Install

npx -y skills add mustafa3252/vibe-ship-skills --skill bug-replay

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Force the agent to reproduce a bug with a tiny loop before attempting fixes.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

1.8 KB, as published. Nobody here has run it

Bug Replay

What this skill does

Force the agent to reproduce a bug with a tiny loop before attempting fixes.

Use it when you want AI speed without the usual vibe-coding tax: vague scope, broken demos, missing tests, or code that looks done but cannot ship.

Operating mode

Name the outcome — one sentence, user-visible, demoable.
List constraints — stack, files to avoid, style, deadline, and non-goals.
Create a tiny proof loop — test, script, screenshot, curl command, or manual checklist.
Build one vertical slice — no speculative framework work.
Verify out loud — report the exact command or evidence that proves the slice works.

Prompt template

Use the Bug Replay skill.
Goal: <what I want built or improved>
Context: <repo/app/user/problem>
Constraints: <stack, files, time, style>
Done means: <observable proof>
Do not: <scope traps or risky changes>

Anti-patterns this skill blocks

Starting with a folder explosion instead of a working slice.
Accepting generated code without a verification loop.
Rewriting the app to fix one small issue.
Shipping a README claim that no command has proven.
Letting the agent hide uncertainty behind confident prose.

Done checklist

The request has a one-line success condition.
The agent knows what not to change.
There is at least one concrete verification step.
The final answer includes evidence, not vibes.

Part of Vibe Coder Skills by Mustafa — Instagram: @mustafaiscoding, X/Twitter: @mustafa30.