Repository navigation
Prototype adversarial review workflow as a cmux skill - #13517
Conversation
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. Note Currently processing new changes in this PR. This may take a few minutes, please wait... ⚙️ Run configurationConfiguration used: Repository: manaflow-ai/cmux/.coderabbit.yaml Review profile: ASSERTIVE Plan: Advanced Run ID: 📒 Files selected for processing (3)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
All contributors have signed the CLA ✍️ ✅ |
|
@codex review |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
|
Squashed onto current main after #13517 merged.
* Add no-socket review ledger CLI Squashed onto current main after #13517 merged. * fix(review-cli): sort receipts by parsed creation instant * fix(review-cli): scope help options to review subcommands * test(review-cli): isolate git env and harden ledger probes * Fix review CLI macOS canonical path fixture * Align review help probe with displayed commands
Summary
cmux-reviewagent skill that turns review into a staged protocol: review brief → intent compliance → independent discovery → triage → adversarial challenge → executable verification → optional repair/reviewcommand that invokes the same repo-owned workflowWhy this first
This intentionally prototypes the review semantics and UX before native model/runtime integration.
cmux already has diff comments, review workspace state, Vault checkpoints/forks, repo review rules, and agent skills. A skill lets the team dogfood:
Those traces can then drive the native review-ledger/socket design instead of freezing a schema from a whiteboard.
Core principle:
Evidence policy
Model agreement is supporting signal. Reproduction, executable checks, verified call paths, and concrete counterexamples carry more weight.
Generated tests are treated as claims too: a passing generated test becomes strong repair evidence only when the workflow establishes that it actually distinguishes defective and repaired behavior.
Receipt behavior
Review receipts live under the repository's Git metadata path returned by:
They carry exact base/head/diff identity plus review policy/ruleset identity and must never enter source control.
Testing
Part of #13510
Summary by CodeRabbit