autoreview: default review effort to high, escalate to xhigh for high-risk diffs

[justin808]

What

Make the autoreview skill run codex review at high reasoning effort by default and reserve xhigh for the high-risk categories the skill already defines.

Why

Review currently inherits the global model_reasoning_effort (xhigh) on every diff. high is the cost-effective depth for routine diffs and does not stall the review loop — full depth is kept exactly where regressions are most likely (hosted-CI-ready, force-full hosted-CI, benchmark categories).

Changes

• Step 3: define effort="${CODEX_REVIEW_EFFORT:-high}" and pass -c model_reasoning_effort="$effort" on all codex review invocations (the key mirrors config.toml).
• High-risk second pass: set the primary review to xhigh first for high-risk diffs.
• Per-environment override via CODEX_REVIEW_EFFORT.

Portable: no repo-specific values; -c composes with --base/--uncommitted/--commit (it is a config override, not focus text).

Validation

bin/validate passes (89 tests across the helper suites, RuboCop clean).

🤖 Generated with Claude Code

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.

[coderabbitai]

Warning

Review limit reached

@justin808, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 37 minutes and 44 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 0c134adc-5e00-41e2-a8f4-f2b0575e28c5

📥 Commits

Reviewing files that changed from the base of the PR and between a2123e6 and e9b2cb6.

📒 Files selected for processing (1)

• skills/autoreview/SKILL.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch jg/autoreview-review-effort

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}