test-before-ship
Use this skill when implementing a new feature or fixing a bug. Write or update tests before marking the task done. Never consider code complete without verifying it works through automated tests.
73
Quality
91%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Securityby
Passed
No findings from the security scan
Test Before Ship
Test pyramid:
- Unit tests for pure functions and business logic (fast, many).
- Integration tests for service interactions and DB queries (medium).
- End-to-end tests for critical user journeys (slow, few).
Test quality checklist:
- Does the test actually fail when the code is broken?
- Does it cover the happy path AND the most likely error cases?
- Is the test name descriptive enough to diagnose a failure from the name alone?
For bug fixes: add a regression test that reproduces the bug before fixing it.
Anti-patterns:
- Tests that only test the mock, not the real behavior.
- Skipping tests because "it probably works".
- Repository
- aiming-lab/MetaClaw
- Commit
922caf3
- Last updated
- First committed
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.