Skip to content
Development
Command

/rtk-test-before-merge

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

From plugin
rtk
80k13 skills6 agents13 commands
Install
$ npx -y skills add rtk-ai/rtk --agent claude-code

How it fires

How this command gets triggered: by you, by Claude, or both.

  • Fires itselfClaude auto-loads it when your prompt matches the work.
  • You can call itInvoke it directly when you want it.
  • Slash command/rtk-test-before-merge

Context preview

What this command does when you run it.

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

Command definition

rtk-test-before-merge.md

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

Test before merge

For every code change that affects observable behaviour:

1. Identify the existing test that covers the area. If none, propose creating it (note the gap in the response). 2. Write the failing test FIRST in a separate commit named `test: <what>` — verify it fails on main, passes on the branch. 3. The implementation commit comes second. 4. If the change is purely refactoring, run the existing tests and report the count + duration; do not add new tests just to satisfy this rule when there is no behaviour change.

Skip is allowed only when:

  • Tweaking a doc string, comment, log message
  • Renaming a private symbol
  • A pre-existing TODO points at "test added in #issue-N"
Ships withrtk

CLI proxy that reduces LLM token consumption by 60-90% on common dev commands. Single Rust binary, zero dependencies

Get the whole plugin

Other commands on rtk.