chore(ci): tune CodeRabbit review budget to stay under plan limits - #93
Merged
Conversation
Our Pro Plus plan is not unlimited — it applies adaptive per-developer limits once recent activity reaches the 95th percentile among CodeRabbit users. We crossed that on 2026-07-19 (15 PRs merged in a day). PR #92 was never reviewed as a result, and its status check still reported "pass / Review completed": a skipped review is indistinguishable from a clean one. Usage-based billing is deliberately not enabled, so the lever is volume. Two changes, both narrow: - auto_incremental_review: false — the default re-runs a full review on every push, so our rebase-on-feedback loop burns three or four reviews per PR for one set of findings. One review per PR, no loss of coverage. - ignore_title_keywords: chore(ci), docs(status) — mechanical PRs with nothing for a reviewer to find. Deliberately narrow substring matches so chore(engine) and docs(modules) are still reviewed. Specs stay in scope on purpose: PR #87 was docs-only and CodeRabbit found nine real defects in it. Prose in this repo carries engineering substance. Config validated against CodeRabbit's published JSON schema (ajv, draft2020) rather than written from assumption. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
Important Review skippedIgnore keyword(s) in the title. ⛔ Ignored keywords (2)
Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Pro Plus is not unlimited. CodeRabbit applies adaptive per-developer limits once recent review activity hits the 95th percentile among its users. We crossed that on 2026-07-19 — 15 PRs merged in one day — and #92 went entirely unreviewed as a result.
The part that matters: its status check still reported
pass / Review completed. A skipped review is indistinguishable from a clean one.@coderabbitai reviewwas also a no-op, since it counts the rate-limited run as having already reviewed the commit.Usage-based billing is deliberately not enabled, so the only lever is volume.
What changed
Two narrow settings in a new
.coderabbit.yaml:auto_incremental_review: falseignore_title_keywords: ["chore(ci)", "docs(status)"]chore(engine)anddocs(modules)still get reviewed.Since the limit is a rolling window, roughly halving consumption should get us back under it.
What deliberately did not change
Specs stay in review scope. The obvious saving would be excluding docs PRs, but the evidence says that's backwards: #87 was docs-only and CodeRabbit found nine real defects — CSRF on key rotation, license↔module binding, webhook idempotency keyed on the wrong field. Prose in this repo carries engineering substance; that's where the review earns its cost.
Verification
ajv-cli(draft2020) →valid. Both key names confirmed against the schema rather than written from assumption; the schema setsadditionalProperties: false, so a wrong key would be a hard error..coderabbit.yamlexisted before this — the rate-limit comment confirmedConfiguration used: defaults.Note
Policy point that outlives this config: the CodeRabbit check should not be treated as a merge gate. Even tuned, a heavy day can exhaust the limit and the check still renders green. The real gate is the tiered review escalation in
.claude/rules/delegation-ladder.md.Also worth flagging: this PR's own title starts with
chore(ci), so once merged, future PRs like it skip review. That's intended, but it means this file's future changes won't be bot-reviewed.🤖 Generated with Claude Code