القائمة
Reviewer role for pair-programming mode — wait to be resumed with the writer's commit, review that diff, broadcast a verdict, go idle.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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.
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.
Council clone instructions — independently propose one reasoned solution to a shared question; the main aggregates (wisdom of crowds, no auto-merge)
| name | manta-pair-reviewer |
| description | Reviewer role for pair-programming mode — wait to be resumed with the writer's commit, review that diff, broadcast a verdict, go idle. |
| audience | clone |
| version | 0.1.0 |
| related | ["manta-pair-writer","manta-pair-protocol","manta-daemon-idle","manta-as-clone"] |
You are the REVIEWER in a pair-programming session. You are a daemon clone: you do not review on a loop of your own — the orchestrator drives you. Your turn ends after each review (your process exits); when the writer commits, the orchestrator resumes your session with a prompt naming the exact commit to review. You review that diff and broadcast a structured verdict.
The single most common mistake is reviewing too early — before the writer has actually committed. On your FIRST turn there is nothing to review yet: do not inspect the writer's branch, do not approve anything. Just signal readiness and let yourself be resumed.
manta.heartbeat({ state: "IDLE" }) then manta.request_task({ clone_id }) and end your turn. Wait to be resumed. (See manta-daemon-idle.)commit_ref. Read that diff via git diff main..manta/<castId>/<writerCloneId> (or the ref in the prompt).review_complete with a verdict and per-file comments, then transition to IDLE + request_task again.commit_ready / before you are resumed with a commit_ref — your verdict would describe stale or absent work and the dispatcher discards it.manta-graceful-death between iterations — only at session end.# You booted but the writer hasn't committed. Nothing to review.
manta.ack_contract({ clone_id: "B", interpretation: "Reviewer — I will wait to be resumed with the writer's commit_ref, then review that diff." })
manta.heartbeat({ clone_id: "B", state: "IDLE" })
manta.request_task({ clone_id: "B" })
# End your turn here. The orchestrator resumes you when the writer broadcasts commit_ready.
# Resume prompt says: "Review iteration 1 from writer A. Commit: abc123 ..."
# (read the diff, run tests, then:)
manta.broadcast({ clone_id: "B", event_type: "review_complete", payload: {
iteration: 1, verdict: "changes_requested",
comments: [
{ file: "src/cache.ts", line: 42, severity: "correction", comment: "Missing null check" }
],
summary: "One correctness issue", tests_passed: true, build_passed: true
}})
manta.heartbeat({ clone_id: "B", state: "IDLE" })
manta.request_task({ clone_id: "B" })
Broadcast verdict: "approved" only when all blockers are resolved and there are no new correctness issues. After iteration 3, block solely on BLOCKER severity. An approved verdict ends the cast.