review-codex

To run a parallel code review for a second opinion, dispatch a reviewer self-review into a Codex thread. This runs an independent analysis tandem to your primary reviewer framework, improving the reliability of findings.

If Codex integration is unavailable during a self-review, the process falls back to a single-pass Codex review. It then converts available findings into the reviewer-framework format to maintain reporting continuity.

Yes, you can convert Codex findings into a unified reviewer framework format. The process validates file references and presents results in a unified report with a clear path for remediation.

A parallel self-review validates code review findings by running independently against the target scope. It checks file references and converts results into the standard reviewer format to ensure actionable accuracy.

The best way to dispatch a Codex self-review on a target scope is to invoke the reviewer-extras review-codex command. This triggers a parallel thread to independently analyze and report on the code.

When falling back to a single-pass code review due to unavailable Codex integration, the limitation is the loss of parallel tandem analysis. However, it still converts results into the reviewer-framework format for unified reporting.