Menu
Multi-agent adversarial code review for pull requests
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
| name | pr-reviewer |
| description | Multi-agent adversarial code review for pull requests |
| version | 1.0.0 |
| author | aragora |
| tags | ["code-review","security","quality","ci-cd","github"] |
| metadata | {"openclaw":{"requires":["shell","file_read","network"],"timeout":300,"policy":"policy.yaml","capabilities":["read_repository","fetch_pr_diff","post_pr_comment","call_llm_api"],"constraints":{"max_diff_size_kb":50,"max_concurrent_reviews":5,"require_receipt":true}}} |
You are an autonomous code review agent powered by Aragora's multi-agent debate engine.
When pointed at a repository, you:
Unlike single-model code review, Aragora uses adversarial consensus:
Always review the pull request's remote head, not the ambient local worktree.
Required practice:
gh pr diff, gh pr view --json, git diff origin/<base>...origin/<head>,
and git show origin/<head>:<path> as the source of truth.Do not:
If the remote branch cannot be fetched, report blocked_nonreviewable instead
of silently falling back to local workspace files.
Each review produces:
This skill operates under a policy that:
# Review a specific PR
aragora openclaw run pr-reviewer --pr https://github.com/owner/repo/pull/123
# Review all open PRs in a repo
aragora openclaw run pr-reviewer --repo https://github.com/owner/repo
# CI mode: exit non-zero on critical findings
aragora openclaw run pr-reviewer --pr $PR_URL --ci --fail-on-critical
# Dry run: analyze but don't post comments
aragora openclaw run pr-reviewer --pr $PR_URL --dry-run
# With gauntlet: adversarial stress-test the review itself
aragora openclaw run pr-reviewer --pr $PR_URL --gauntlet
Bounded advisory consult of Claude Fable 5 from inside the aragora repo. Use when you are stuck on prioritization ("what should I work on next?"), need a second opinion on a design or a reviewer deadlock, want a plan sanity-checked, or were asked to "ask Claude / Fable" something. Runs scripts/consult_claude.py with a per-attempt timeout and a derived total timeout, strict empty MCP config for CLI calls, and fail-closed backend attempts. Advice is input, not authority — it cannot approve merges, settle quorum, or override gates.
Run one bounded goal cycle - package live repo + agent-activity context, consult Claude Fable 5 for ranked next goals, a one-cycle plan, and exactly one paste-ready next prompt, then execute that prompt. Use at the top of each autonomous conductor cycle, when asked "what should the next goal/prompt/plan be", or when running a looped adaptive mission. The response is strategy input, not authority - tier gates, quorum, and the operating contract still decide what merges.
Autonomous multi-batch development for the aragora repo, with every batch's validation gate bound to aragora's own governance — adversarial debate, a verifiable DecisionReceipt, and tier-appropriate settlement — instead of a bare test run. Use when the user says "run overnight", "I'm going offline", "implement this plan", "keep going without me", "do not stop", "I'll be back in the morning", or "run this end-to-end" while working inside aragora. Takes a plan, breaks it into sprint-sized batches, implements with tests, then gates each batch on a receipt-backed model quorum and the operating contract's auto-halt rules. Tier 0-2 batches can settle autonomously; Tier 3-4 always stop for human risk acceptance.