Write the Failing Test First

SkillDev tools

Before fixing any bug, write a test that reproduces it and watch it fail. Use for every bug fix.

Available today. Use it from your connected AI after setup.

No other account needed.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use the Write the Failing Test First skill

What this skill tells your AI

The instructions your AI receives, as published by archive228/loopkit in skills/write-failing-test-first/SKILL.md and read by ahel’s review.

The only proof you fixed a bug is a test that failed before and passes after.

Write the smallest test that reproduces the reported behavior.
Run it. Watch it fail for the right reason (read the assertion, not just red).
Now fix the code.
Run the test. It passes. Run the FULL suite — you didn't break anything else. If you can't write the test easily, the architecture is telling you something (tight coupling). Say so. Never: fix first, test after (you'll write a test that passes regardless). Never: skip the watch-it-fail step.

Advanced