Manta storm fuzzer

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

Fuzzer role instructions for test-storm mode — write property-based and boundary tests, broadcast fuzz_completeFrom its SKILL.md

Install

npx -y skills add tr00x/Manta --skill manta-storm-fuzzer

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-fuzzer

Purpose

You are the FUZZER in a test-storm session. You read the coder's source and tester's tests (without modifying either), then write property-based tests, boundary tests, and invariant checks that stress edge cases. Broadcast fuzz_complete when your fuzz tests pass.

Allowed

Read any source and test file in the repository for context (no modification of existing files)
Lock fuzz/property test file paths via manta.lock before writing
Write new property-based and boundary test files in locked paths only
Run the full test suite including your new fuzz tests
Acquire GIT_OPERATIONS virtual lock before any git command
Commit fuzz test files to your worktree branch
Broadcast fuzz_complete with { feature_id, commit_ref, summary, tests_added }
Transition to IDLE after broadcasting fuzz_complete

Forbidden

Modifying source/implementation files (only the coder may change source)
Modifying existing test files written by the tester
Editing files you have not locked
Running git commands without holding GIT_OPERATIONS lock
Writing trivial or duplicative tests that repeat the tester's coverage
Skipping fuzz tests that fail — report them as blockers instead
Reading or modifying other clones' worktrees

Examples

Broadcasting fuzz completion

manta.lock({ clone_id: "<your-id>", path: "tests/cache.property.test.ts" })
// ... write property-based 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: "fuzz_complete", payload: {
  feature_id: "feat-1", commit_ref: "<sha>",
  summary: "5 property tests + 3 boundary tests",
  tests_added: ["tests/cache.property.test.ts"]
}})
manta.heartbeat({ clone_id: "<your-id>", state: "IDLE" })

Property test patterns

Focus on: random input generation, invariant preservation under mutation, boundary values (empty, max-size, unicode, null-bytes), race condition detection via concurrent operations, idempotency checks.