From teams
Report on CodeRabbit adoption across OCP payload repos
How this command is triggered — by the user, by Claude, or both
Slash command
/teams:coderabbit-adoption-report [--start-date YYYY-MM-DD] [--end-date YYYY-MM-DD]The summary Claude sees in its command listing — used to decide when to auto-load this command
## Name teams:coderabbit-adoption-report ## Synopsis ## Description The `teams:coderabbit-adoption-report` command measures CodeRabbit Pro adoption across a curated list of ~160 OCP payload repositories by calculating what percentage of merged PRs received a Pro-tier CodeRabbit review (identified by `"Plan: Pro"` in the comment body). The list of repos to scan is defined in `plugins/teams/skills/coderabbit-adoption/allowed-repos.txt`. It uses a Python script that calls the GitHub search API via `gh` CLI. The script does one org-wide query for PRs with Pro reviews, then batched queri...
teams:coderabbit-adoption-report
/teams:coderabbit-adoption-report
/teams:coderabbit-adoption-report --start-date 2026-02-01 --end-date 2026-02-28
The teams:coderabbit-adoption-report command measures CodeRabbit Pro adoption across a curated list of ~160 OCP payload repositories by calculating what percentage of merged PRs received a Pro-tier CodeRabbit review (identified by "Plan: Pro" in the comment body).
The list of repos to scan is defined in plugins/teams/skills/coderabbit-adoption/allowed-repos.txt.
It uses a Python script that calls the GitHub search API via gh CLI. The script does one org-wide query for PRs with Pro reviews, then batched queries (20 repos per batch) for all merged PRs. Per-repo breakdowns are calculated in Python. Takes about a minute to complete with progress shown.
CodeRabbit was enabled across most OCP payload repos on 2026-03-09. Since many of these repos are open source, CodeRabbit may leave comments on any PR — but only Pro reviews (indicated by Plan: Pro in the CodeRabbit comment) provide the full-quality analysis we want.
CodeRabbit does not review bot PRs. PRs authored by bot accounts (e.g., dependabot[bot], github-actions[bot], openshift-monitoring-bot[bot]) are intentionally skipped by CodeRabbit. Bot PRs appearing in the "missed" list are expected and should not be counted against adoption.
The script uses "Plan: Pro" as a search term combined with commenter:coderabbitai[bot] to directly identify Pro-reviewed PRs, then compares against all merged PRs to find the gap.
The script filters to PRs created on or after the enablement date (2026-03-09) to avoid counting old long-lived PRs that merged after enablement but were never seen by CodeRabbit.
--start-date YYYY-MM-DD (optional): Start of the date range for merged PRs. Defaults to 7 days ago.--end-date YYYY-MM-DD (optional): End of the date range for merged PRs. Defaults to today.gh): Must be installed and authenticated with access to the openshift org.Verify prerequisites:
gh auth status
python3 --version
Run the Python script with arguments passed through from the command.
# Default (last 7 days)
python3 plugins/teams/skills/coderabbit-adoption/coderabbit_adoption.py
# With date range
python3 plugins/teams/skills/coderabbit-adoption/coderabbit_adoption.py \
--start-date 2026-02-01 --end-date 2026-02-28
The script handles all GitHub API orchestration:
commenter:coderabbitai[bot] "Plan: Pro", filtered to allowed repos.All queries include a created:>=2026-03-09 filter to exclude PRs opened before CodeRabbit was enabled.
Parse the JSON output and format the report. The script outputs all data needed: summary stats, missed PRs with URLs, and per-user breakdowns.
Detect partial data: Check if truncated is true. When true, GitHub search pagination hit its limits (1000 items max). Insert a warning notice in the report.
## CodeRabbit Adoption Report
**Date Range**: <start_date> to <end_date>
**PRs created on or after**: <cr_enablement_date>
### Summary
- Repos scanned: <total_allowed_repos>
- Repos with activity: <repos_with_activity>
- Total merged PRs: <total_merged_prs>
- PRs with Pro review: <prs_with_pro_review>
- Adoption rate: <adoption_pct>%
### PRs Without Pro Review (<missed_prs_count>)
| Repository | PR | Author | Bot? |
|---|---|---|---|
| openshift/console | [#16138](https://github.com/openshift/console/pull/16138) | rhamilto | No |
| openshift/ironic-image | [#816](https://github.com/openshift/ironic-image/pull/816) | github-actions[bot] | Yes |
### Users Without Pro Reviews (<count>)
Users who authored merged PRs but whose PRs did not receive a Pro CodeRabbit review.
Bot accounts are excluded.
| User | Repos |
|---|---|
| @username | openshift/repo-a, openshift/repo-b |
### Repos with No Activity
<repos_without_activity_count> repos had no merged PRs in this date range.
Offer to copy report to clipboard: After presenting the report, ask the user if they'd like the full markdown report copied to their clipboard. If they accept, use pbcopy (macOS) or xclip/xsel (Linux) to copy the complete report.
AI Analysis: After presenting the data, provide brief observations:
Default (last 7 days):
/teams:coderabbit-adoption-report
Specific month:
/teams:coderabbit-adoption-report --start-date 2026-02-01 --end-date 2026-02-28
plugins/teams/skills/coderabbit-adoption/allowed-repos.txt are included. Edit that file to change scope. The list can be regenerated from a release payload with:
oc adm release info --commits 4.12.0 -o json | \
jq '.references.spec.tags[].annotations["io.openshift.build.source-location"]' -r | \
uniq | sort -u > plugins/teams/skills/coderabbit-adoption/allowed-repos.txt
CR_ENABLEMENT_DATE and prevents old long-lived PRs from skewing adoption numbers.gh api -X GET for all GitHub API calls (the -X GET flag is required for the search endpoint)."Plan: Pro" as a search term combined with commenter:coderabbitai[bot] to directly identify Pro-reviewed PRs via GitHub's full-text search./teams:coderabbit-inheritance-scanner - Scan repos for CodeRabbit config inheritancenpx claudepluginhub saschagrunert/ai-helpers --plugin teams/coderabbit-adoption-reportMeasures CodeRabbit Pro adoption across ~160 OCP payload repos by calculating the percentage of merged PRs that received a Pro-tier review.