velesnitski

Rtk Test Before Merge — Testing skill for Claude Code

Testing community

Force the agent to write or extend a test for every behaviour change.

How to install Rtk Test Before Merge

Installs to ~/.claude/commands/velesnitski-rtk-rtk-test-before-merge.md

Terminal

mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/velesnitski/rtk/HEAD/.claude/commands/rtk-test-before-merge.md -o ~/.claude/commands/velesnitski-rtk-rtk-test-before-merge.md

Restart Claude Code, or start a new session, for it to be picked up.

What Rtk Test Before Merge does

Force the agent to write or extend a test for every behaviour change.

Test before merge

For every code change that affects observable behaviour:

Identify the existing test that covers the area. If none, propose creating it (note the gap in the response).
Write the failing test FIRST in a separate commit named test: — verify it fails on main, passes on the branch.
The implementation commit comes second.
If the change is purely refactoring, run the existing tests

Alternatives in Testing

/test Routing — Vérifie le routing de commandes RTK sans exécution (dry-run) 25.5k ★
Pua — Use when the user invokes /pua or asks for PUA mode, try-harder/retry help, change-approach coaching, completi 19.5k ★
Testing Strategy — This project is small, runs in a terminal, and is mostly deterministic 10.9k ★