cross-review
From omnigent-ai
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.
Dispatches a different-vendor sub-agent to review a diff against its contract and loops fixes until clean.
Use it when
- Verifying an implementer's PR/diff before merge with independent review
- Enforcing that tests/lint/typecheck pass before any review happens
- Routing blocking review issues back to the same implementer session for fixes
Skip it if
- Only one worker or one vendor is available on the machine
- Requires polly's orchestration tools (sys_os_shell, sys_session_send, sys_read_inbox, task registry)
- You don't run multiple AI coding vendors (claude_code, codex, opencode, cursor, hermes, pi)
Facts
- Repository
- omnigent-ai/omnigent
- Status
- Actively maintained
- Last commit
- Source file
- examples/polly/skills/cross-review/SKILL.md
Source preview
The instructions Claude Code reads when this skill runs.
# cross-review — independent verification
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.
## Procedure
1. Get the task's diff — `sys_os_shell("gh pr diff <pr>")` (or
`git -C .worktrees/<task_id> diff main...HEAD`).
2. Run the deterministic gates first — tests / lint / typecheck via
`sys_os_shell`. If red, re-dispatch the implementer to drive it green first;
don't involve the reviewer yet.
3. Dispatch a DIFFERENT-vendor sub-agent as reviewer: pick any AVAILABLE worker
whose vendor differs from the implementer's — `claude_code`, `codex`,
`opencode`, `cursor`, `hermes`, or `pi` (e.g. Claude built it → any of
`codex` / `opencode` / `cursor` / `hermes` / `pi`, and so on). Use a
task-based title such as `review-auth-refactor`, never the raw vendor name:
`sys_session_send(agent="claude_code"|"codex"|"opencode"|"cursor"|"hermes"|"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
tuView full source on GitHub →Other skills
django-tdd
★ 229,918Django testing strategies with pytest-django, TDD methodology, factory_boy, mocking, coverage, and testing Django REST Framework APIs.
affaan-mupdated 15d agoMITclickhouse-io
★ 229,918ClickHouse database patterns, query optimization, analytics, and data engineering best practices for high-performance analytical workloads.
affaan-mupdated 15d agoMITlaravel-patterns
★ 229,918Patrones de arquitectura Laravel, routing/controladores, Eloquent ORM, capas de servicio, colas, eventos, caché y API resources para aplicaciones en producción.
affaan-mupdated 15d agoMITverification-loop
★ 229,918Sistema de verificación completo para sesiones de Claude Code.
affaan-mupdated 15d agoMITstrategic-compact
★ 229,918Suggests manual context compaction at logical intervals to preserve context through task phases rather than arbitrary auto-compaction.
affaan-mupdated 15d agoMITfrontend-patterns
★ 229,918Patrones de desarrollo frontend para React, Next.js, gestión de estado, optimización de rendimiento y buenas prácticas de UI.
affaan-mupdated 15d agoMIT