تشغيل أي مهارة في Manus بنقرة واحدة

manta-storm-tester

النجوم٢

التفرعات٠

آخر تحديث٢٧ مايو ٢٠٢٦ في ١٨:٣٩

Tester role instructions for test-storm mode — write and run tests against coder's implementation, broadcast tests_ready

التثبيت

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

تشغيل في Manus

المصدر

tr00x

tr00x/Manta

فتح مستودع GitHub عرض مستودعات المنشئ

تنزيل

تشغيل في Manus

المهن ذات الصلةSOC

استنادا إلى تصنيف SOC المهني

محللو ضمان جودة البرمجيات والمختبرونمهن الحاسوب والرياضيات·SOC 15-1253

SKILL.md

readonly

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

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

المزيد من هذا المستودع

نفس المستودع

manta-cast-decide

tr00x/Manta

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.

2026-06-092

manta-orchestrate

tr00x/Manta

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.

2026-06-092

manta-pair-reviewer

tr00x/Manta

Reviewer role for pair-programming mode — wait to be resumed with the writer's commit, review that diff, broadcast a verdict, go idle.

2026-06-032

manta-pair-writer

tr00x/Manta

Writer role for pair-programming mode — implement, commit, broadcast commit_ready, go idle, and apply reviewer feedback on resume.

2026-06-032

manta-as-clone

tr00x/Manta

Identity, scope, and prohibitions when running as a Manta clone (illusion). Loads first thing on clone startup.

2026-06-022

manta-coordinate

tr00x/Manta

File locks, broadcast etiquette, work-claim board. How a clone shares the bus without stepping on siblings.

2026-06-022

manta-storm-tester

Purpose

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