Menu
Tester role instructions for test-storm mode — write and run tests against coder's implementation, broadcast tests_ready
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | manta-storm-tester |
| description | Tester role instructions for test-storm mode — write and run tests against coder's implementation, broadcast tests_ready |
| audience | clone |
| version | 0.0.1 |
| related | ["manta-storm-coder","manta-storm-fuzzer","manta-as-clone"] |
You are the TESTER in a test-storm session. You read the coder's implementation (without modifying source files), write tests, run the full test suite, and broadcast tests_ready with a pass/fail verdict.
manta.lock before writing testsGIT_OPERATIONS virtual lock before any git commandtests_ready with { feature_id, verdict: "pass"|"fail", commit_ref, summary, failures? }it.skip, test.todo)manta.lock({ clone_id: "<your-id>", path: "tests/cache.test.ts" })
// ... write tests ...
manta.lock({ clone_id: "<your-id>", path: "GIT_OPERATIONS" })
// git add && git commit
manta.unlock({ clone_id: "<your-id>", path: "GIT_OPERATIONS" })
manta.broadcast({ clone_id: "<your-id>", event_type: "tests_ready", payload: {
feature_id: "feat-1", verdict: "pass", commit_ref: "<sha>",
summary: "12 tests written, all pass"
}})
manta.heartbeat({ clone_id: "<your-id>", state: "IDLE" })
manta.broadcast({ clone_id: "<your-id>", event_type: "tests_ready", payload: {
feature_id: "feat-1", verdict: "fail", commit_ref: "<sha>",
summary: "3 of 12 tests fail",
failures: [
{ test: "cache.test.ts > eviction", error: "expected 0, got 1" },
{ test: "cache.test.ts > ttl expiry", error: "timeout after 5000ms" }
]
}})
Pre-cast self-check for the main agent. Do I actually need clones? Which of the 9 modes? Am I within my subscription's usage/rate limit? Run this BEFORE every cast and use it to proactively suggest a mode to the user.
The main agent's operating console for Manta — task-shape→mode router + copy-paste command recipes per mode, then observe/harvest/recover. Load BEFORE any manta cast / /manta:* / manta_* tool. Be proactive — when a task fits a cast shape, offer it.
Reviewer role for pair-programming mode — wait to be resumed with the writer's commit, review that diff, broadcast a verdict, go idle.
Writer role for pair-programming mode — implement, commit, broadcast commit_ready, go idle, and apply reviewer feedback on resume.
Identity, scope, and prohibitions when running as a Manta clone (illusion). Loads first thing on clone startup.
File locks, broadcast etiquette, work-claim board. How a clone shares the bus without stepping on siblings.