agentsclimarketplace

Manta storm tester

Skill tr00x/Manta/skills/manta-storm-tester

Tester role instructions for test-storm mode — write and run tests against coder's implementation, broadcast tests_readyFrom its SKILL.md

Install
npx -y skills add tr00x/Manta --skill manta-storm-tester

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.3 KB, as published. Nobody here has run it

manta-storm-tester

Purpose

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.

Allowed

  • Read any source file in the repository for context (no modification)
  • Lock test files via manta.lock before writing tests
  • Write test files in locked test directories only
  • Run the full test suite against the coder's changes
  • Acquire GIT_OPERATIONS virtual lock before any git command
  • Commit test files to your worktree branch
  • Broadcast tests_ready with { feature_id, verdict: "pass"|"fail", commit_ref, summary, failures? }
  • Transition to IDLE after broadcasting tests_ready
  • Re-test after coder applies fixes (new cycle via resume prompt)

Forbidden

  • Modifying source/implementation files (only the coder may change source)
  • Editing files you have not locked
  • Running git commands without holding GIT_OPERATIONS lock
  • Approving tests that have known failures without reporting them
  • Writing test stubs or skipped tests (it.skip, test.todo)
  • Reading or modifying other clones' worktrees

Examples

Broadcasting test results (pass)

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" })

Broadcasting test results (fail)

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" }
  ]
}})

Keep looking

Skills are one crate of 627,801. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.