Add CodeRabbit configuration

[esthor]

Summary

• Add .coderabbit.yaml to enable assertive AI reviews, request-changes workflow, draft reviews, simplify finishing touches, 100% docstring pre-merge threshold, and issue enrichment with auto-labeling

Test plan

• Open a follow-up PR and confirm CodeRabbit picks up the config (assertive profile, draft auto-review, simplify suggestions)
• Confirm issue enrichment runs on a new issue

🤖 Generated with Claude Code

Summary by CodeRabbit

• Chores
  • Added automation to enhance code review and issue workflows: early-access review mode, assertive review profile with request-changes enforcement (failing commits on failed checks), automatic label application and reviewer assignment, auto-review for drafts, automatic issue enrichment, and pre-merge docstring checks (threshold 80). Also adjusted generation preferences (disabled unit test generation, enabled code simplification).

Note: No user-facing changes.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
allthingsweb	Ready	Preview, Comment	Apr 24, 2026 10:21pm

[coderabbitai]

Warning

Ignoring CodeRabbit configuration file changes. For security, only the configuration from the base branch is applied for open source repositories.

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository UI (base), Organization UI (inherited)

Review profile: ASSERTIVE

Plan: Pro

Run ID: 0287f431-0436-4393-8a83-1c82e8664e41

📥 Commits

Reviewing files that changed from the base of the PR and between fba3271 and 692d822.

📒 Files selected for processing (1)

• .coderabbit.yaml

---

📝 Walkthrough

Walkthrough

Adds a new .coderabbit.yaml to configure CodeRabbit automation: review profile and workflow, automatic labeling and reviewer assignment, draft PR auto-review, code simplification, docstring pre-merge checks, and issue enrichment.

Changes

Cohort / File(s)	Summary
CodeRabbit Configuration .coderabbit.yaml	Adds a new CodeRabbit automation config enabling early-access features, assertive/request-changes review profile, commit failure on review failures, automatic label application and reviewer assignment, draft PR auto-review, code simplification, disabling unit-test generation, docstring pre-merge checks with 80% threshold (warnings), and automatic issue enrichment.

Sequence Diagram(s)

sequenceDiagram
    participant Dev as Developer (opens PR)
    participant CR as CodeRabbit Automation
    participant Repo as Repository
    participant Rev as Assigned Reviewers
    participant CI as Pre-merge Checks

    Dev->>Repo: Open PR (may be draft)
    Repo->>CR: Trigger automation (PR event)
    CR->>Repo: Apply labels & assign reviewers
    CR->>Rev: Request review (assertive / request-changes)
    CR->>CI: Run pre-merge checks (docstring threshold, simplification)
    CI-->>CR: Report results (pass/warn/fail)
    CR->>Repo: Mark commits failed if review checks fail
    CR->>Repo: Enrich related issues automatically

Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐰 A config file hops into view,
Settings aligned, tidy and new,
Labels and reviews on cue,
Checks and notes softly accrue,
I nibble bugs—then bid adieu! 🥕✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Add CodeRabbit configuration' directly and accurately describes the main change: a new .coderabbit.yaml configuration file. It is concise, clear, and specific enough for understanding the primary change.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

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 and usage tips.}

[coderabbitai]

Actionable comments posted: 5

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In @.coderabbit.yaml:
- Line 2: The repository currently enables preview features via the YAML key
early_access: true; to avoid instability revert or disable this opt-in by
changing that key to false or removing it so preview features are not enabled,
or add a comment explaining the intentional tradeoff if you must keep it
enabled; locate the early_access entry in the .coderabbit.yaml and update or
remove it accordingly.
- Line 9: The config sets auto_apply_labels: true but lacks
reviews.labeling_instructions, which will auto-apply labels inferred solely from
prior PRs; either change auto_apply_labels to false to disable automatic
labeling or add a constrained reviews.labeling_instructions block specifying
allowed labels and matching rules so only those labels can be auto-applied (look
for the auto_apply_labels key and the reviews.labeling_instructions section in
the .coderabbit.yaml to make the change).
- Line 10: The config enables auto_assign_reviewers without any guidance rules,
which can cause unexpected reviewer pings; add a
suggested_reviewers_instructions mapping to scope assignments or set
auto_assign_reviewers to false until rules exist. Update the .coderabbit.yaml to
either (a) add a suggested_reviewers_instructions block that maps concrete team
handles and PR patterns to reviewer suggestions so auto_assign_reviewers has
explicit rules, or (b) change auto_assign_reviewers: true to
auto_assign_reviewers: false while you define mappings; reference the
auto_assign_reviewers and suggested_reviewers_instructions keys when making the
change.
- Around line 25-26: The config currently sets auto_apply_labels: true under
labeling which will auto-apply labels without any allow-list; either set
auto_apply_labels to false or add explicit
issue_enrichment.labeling.labeling_instructions that define an allow-list and
clear rules for applying labels. Locate the labeling block (auto_apply_labels)
and either flip it to false or create a labeling_instructions entry under
issue_enrichment.labeling that enumerates permitted labels and matching criteria
so auto-apply only uses the approved list.
- Around line 18-20: pre_merge_checks.docstrings currently sets threshold: 100
but leaves pre_merge_checks.docstrings.mode unspecified (defaulting to
"warning"), which yields permanent warnings; decide and implement one fix:
either set pre_merge_checks.docstrings.mode: error to actually block merges when
request_changes_workflow is true (Option A), or keep mode: warning and lower the
threshold to a realistic percentage (e.g., 80-90) so the check is advisory and
meaningful (Option B); update the YAML accordingly by modifying the
pre_merge_checks.docstrings block to include the chosen mode and, if choosing
Option B, a reduced threshold.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository UI (base), Organization UI (inherited)

Review profile: ASSERTIVE

Plan: Pro

Run ID: 4cf2566a-a168-436b-86bd-3743851de918

📥 Commits

Reviewing files that changed from the base of the PR and between fba3271 and eb5ef70.

📒 Files selected for processing (1)

• .coderabbit.yaml

[esthor]

@coderabbitai full review

[coderabbitai]

✅ Actions performed

Full review triggered.