القائمة
Verify an implementer's diff with an INDEPENDENT, different-vendor sub-agent (diff plus contract only); turn blocking issues into fix-tasks and loop until clean.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack for a new platform.
Run independent subtasks in parallel — one git worktree and one implementation sub-agent per task, each opening its own PR — then cross-review every PR. polly never merges; the human does.
Patterns and templates for generating valid Omnigent agent directories. Load when ready to create files.
Deep reference on Omnigent config format, executor types, skill/tool structure, and conventions. Load when you need to look up how the platform works.
Spin up a live local Omnigent server and exercise the Antigravity (Gemini) SDK harness end-to-end — build antigravity agents, run real turns, smoke-test, and bug-bash. Load when developing, testing, or debugging the antigravity harness (omnigent/inner/antigravity_executor.py, antigravity_harness.py, omnigent/onboarding/antigravity_auth.py) or its auth / model / tool-bridge behavior.
Spin up a live local Omnigent server and exercise the Cursor SDK harness end-to-end — build cursor agents, run real turns, smoke-test, and bug-bash. Load when developing, testing, or debugging the cursor harness (omnigent/inner/cursor_executor.py, cursor_harness.py, cursor_auth.py) or its auth / model / tool-bridge behavior.
| name | cross-review |
| description | Verify an implementer's diff with an INDEPENDENT, different-vendor sub-agent (diff plus contract only); turn blocking issues into fix-tasks and loop until clean. |
The implementer never signs off on its own work — a different model does, and review is a sub-agent that returns a structured report, not a transcript anyone needs to read through.
sys_os_shell("gh pr diff <pr>") (or
git -C .worktrees/<task_id> diff main...HEAD).sys_os_shell. If red, re-dispatch the implementer to drive it green first;
don't involve the reviewer yet.codex or pi; Codex built it → claude_code or pi; Pi built it →
claude_code or codex). Use a task-based title such as
review-auth-refactor, never the raw vendor name:
sys_session_send(agent="claude_code"|"codex"|"pi", title="review-<task_slug>", args={purpose: "review", input: "<the diff> + <the acceptance contract>. Review ONLY against the contract. Report blocking / non-blocking / suggestions. Do not edit code."}). Give it the diff as text — do NOT point
it at the implementer's worktree. Fetch the diff and emit the
sys_session_send call in the SAME turn you decide to review — never end a
turn having only announced "I'll load cross-review and fetch the diff" with
no tool call (that dropped turn stalls the run; nothing dispatches and no
inbox wake arrives). Once the reviewer dispatch is in flight, end your turn;
collect the inbox-delivered structured report with sys_read_inbox when it
returns. Use sys_session_get_history only to debug an empty or unclear
review result.sys_session_send — reuse the original implementer's
agent + title (or address it by session_id) with
purpose: "implement", so the worker keeps its worktree/branch context and
updates its existing PR. A new title would spawn a fresh worker with no
memory of the task. Then loop to step 1.claude_code/codex/pi) dispatched with
purpose: "review" — a DIFFERENT vendor from the one that built the diff. It
reports issues and never edits; only the implementer opens a PR, so a stray
reviewer edit never reaches the deliverable.