What problem does it solve? Single-agent code reviews can miss risks because the same model that wrote the code evaluates it. This Skill sends the current worktree to a second, independent agent in the same workmux session and manages a structured adversarial review dialogue, so findings are challenged and verified before you act on them. ## Core Features & Use Cases - Sibling reviewer selection: Automatically resolves the current tmux session and window, then targets the opposite agent (claude or omp) as the reviewer. - Structured review protocol: Requires the reviewer to cite exact files and lines, rank findings as must-fix, should-fix, or optional, and return "No findings" when evidence is lacking. - Verified reporting: Every sibling finding is checked against the repository before being accepted, rejected, or flagged as unresolved. - Use Case: After implementing a feature in a workmux session, invoke /adreview to have the sibling agent hunt for correctness, security, and performance risks, then receive a verified findings report without any code being modified. ## Quick Start Invoke /adreview with an optional target such as a branch, diff, or set of files to start an adversarial review of the current worktree.