Help us improve
Share bugs, ideas, or general feedback.
From repowire
Requests an independent code/PR/plan review from a different AI agent backend (e.g., Codex reviewing Claude's work) via the repowire mesh. Use for unbiased second opinions before merging.
npx claudepluginhub prassanna-ravishankar/repowire --plugin repowireHow this skill is triggered — by the user, by Claude, or both
Slash command
/repowire:cross-agent-reviewThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Ask a peer running a **different** agent backend to review your work, so the
Multi-agent code review with parallel specialized reviewers, architecture validation, and challenge validation. Automatically activates on PRs, branches, diffs, and review requests.
Enables cross-model code review where a different AI model reviews code written by the current model, reducing self-approval bias. Provides patterns and rules for using Claude Code and Codex CLIs.
Runs cross-LLM iterative code reviews with Codex or Gemini CLI peers, applying accepted fixes until consensus on improved code and report.
Share bugs, ideas, or general feedback.
Ask a peer running a different agent backend to review your work, so the review is genuinely independent (not the same model checking itself).
Pick the reviewer in this order:
repowire config get skills.default_reviewer_backend
(Prints the value, or nothing if unset. --json for the raw value.)You can see who is available and on which backend:
list_peers()repowire peer listask(peer_name, "Review this diff for correctness + bugs: <context>")repowire peer ask is a synchronous test utility, not this).ask is non-blocking and returns a correlation_id. The reviewer closes the
thread with ack(corr_id, <their review>) — that reply comes back to you.ask(reply_to=corr_id, ...) for follow-ups.If no different-backend peer is available and the user wants one, spawn it
(see the delegate skill) — but only with the user's go-ahead.