codexlooplisted

<!-- Generated by scripts/build-adapters.sh. Do not edit directly. --> # Codexloop Drive a GitHub PR until Codex has no unresolved review comments, **but do not cargo-cult its suggestions.** Every comment is a *claim to verify*, not an instruction to obey. A wrong suggestion applied is worse than the comment itself. ## How Codex differs from Greptile / Gemini - **No check-run, no score.** Codex does not publish an `X/5` confidence or a named check. It posts a **PR review** (state `COMMENTED`) plus inline review comments. Detection is by polling the *reviews* endpoint. "Satisfied" = zero unresolved comments (each either fixed or rebutted). - **Trigger phrase is `@codex review`.** Codex reviews automatically when a PR opens or gets new commits if auto-review is enabled on the repo; the mention forces a fresh pass. Other useful mentions: `@codex review focus on <area>` for a scoped re-review. - **Priority, not confidence.** Codex findings usually lead with a severity/priority word (`P1`, `P2`, `P3` or `critical`/`major`/`minor`) or a short titled heading. Weight the top tier seriously; treat the bottom tier as usually-skippable nits unless clearly correct. - **Codex is terse and often reasons from the diff alone.** Its characteristic failure is confidently asserting a bug based only on the changed hunk, without the surrounding file or the call sites. That makes "read the whole file before believing it" the single highest-value check. ## Not for - GitLab / P