MetaClaw 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.

install

source · Clone the upstream repo

git clone https://github.com/aiming-lab/MetaClaw

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/aiming-lab/MetaClaw "$T" && mkdir -p ~/.claude/skills && cp -r "$T/memory_data/skills/test-before-ship" ~/.claude/skills/aiming-lab-metaclaw-test-before-ship && rm -rf "$T"

manifest: memory_data/skills/test-before-ship/SKILL.md

source content

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".