Auto-detect PR reviewers and publish resolution feedback - #27
Conversation
|
Warning Review limit reached
Next review available in: 31 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the 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 reviews. How do review 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 refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (5)
📝 WalkthroughWalkthrough
ChangesShipping PR reviewer and publication flow
Estimated code review effort: 4 (Complex) | ~45 minutes Sequence Diagram(s)sequenceDiagram
participant shipping-pr
participant skill-set-pr
participant GitHub
shipping-pr->>skill-set-pr: initialize and snapshot PR
skill-set-pr->>GitHub: collect reviewer evidence
GitHub-->>skill-set-pr: statuses, reviews, comments, reactions
shipping-pr->>skill-set-pr: publish results and thread feedback
skill-set-pr->>GitHub: validate gate, reply to threads, resolve eligible threads
skill-set-pr->>GitHub: publish summary and derived CodeRabbit resolve command
Possibly related PRs
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
🧹 Nitpick comments (1)
plugins/skill-set/evals/shipping-pr/state-machine-happy-path/fixtures/mock-gh (1)
35-58: 📐 Maintainability & Code Quality | 🔵 Trivial | 💤 Low valueDuplicated GraphQL reply/resolve/node mock logic across two fixture scripts. Both mocks now implement the same
id=/body=argument parsing, the same three-way GraphQL branch (reply/resolve/node), and the same fixture-file persistence side effects.
plugins/skill-set/evals/shipping-pr/state-machine-happy-path/fixtures/mock-gh#L35-L58: extract this block (and the paired reactions/check-runs/status stubs at L75-L89) into a small shared helper script sourced by both mocks.plugins/skill-set/tests/fixtures/mock-gh-pr#L161-L196: source the same shared helper instead of re-implementing the identical parsing/branching logic (and its L223-L260 stub counterparts).🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@plugins/skill-set/evals/shipping-pr/state-machine-happy-path/fixtures/mock-gh` around lines 35 - 58, The GraphQL reply/resolve/node handling and paired reactions, check-runs, and status stubs are duplicated between plugins/skill-set/evals/shipping-pr/state-machine-happy-path/fixtures/mock-gh lines 35-58 and 75-89 and plugins/skill-set/tests/fixtures/mock-gh-pr lines 161-196 and 223-260. Extract the shared argument parsing, GraphQL branches, persistence side effects, and stub logic into one helper script, then source that helper from both mock-gh scripts and remove their duplicate implementations.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Nitpick comments:
In
`@plugins/skill-set/evals/shipping-pr/state-machine-happy-path/fixtures/mock-gh`:
- Around line 35-58: The GraphQL reply/resolve/node handling and paired
reactions, check-runs, and status stubs are duplicated between
plugins/skill-set/evals/shipping-pr/state-machine-happy-path/fixtures/mock-gh
lines 35-58 and 75-89 and plugins/skill-set/tests/fixtures/mock-gh-pr lines
161-196 and 223-260. Extract the shared argument parsing, GraphQL branches,
persistence side effects, and stub logic into one helper script, then source
that helper from both mock-gh scripts and remove their duplicate
implementations.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 31d661c6-435b-48f2-af34-8fd1e4929088
📒 Files selected for processing (15)
CHANGELOG.mdplugins/skill-set/agents/pr-review-feedback.mdplugins/skill-set/agents/resolving-pr-blockers.mdplugins/skill-set/bin/skill-set-prplugins/skill-set/commands/pr/ship.mdplugins/skill-set/evals/shipping-pr/state-machine-happy-path/fixtures/mock-ghplugins/skill-set/evals/shipping-pr/state-machine-happy-path/fixtures/scaffold.shplugins/skill-set/evals/shipping-pr/state-machine-happy-path/prompt.mdplugins/skill-set/skills/shipping-pr/SKILL.mdplugins/skill-set/skills/shipping-pr/reference/blocker-resolution.mdplugins/skill-set/skills/shipping-pr/reference/polling.mdplugins/skill-set/skills/shipping-pr/reference/troubleshooting.mdplugins/skill-set/tests/fixtures/mock-gh-prplugins/skill-set/tests/test-pr-runner.shplugins/skill-set/tests/test-shipping-pr-happy-path-eval.sh
1 participant
Summary
Changes
fixedandaccepted_as_isthreads, leavingunresolvedfeedback open.@coderabbitai resolvecommand only when all queued CodeRabbit items are resolved.Test Plan
/bin/bash plugins/skill-set/tests/run.shgit diff --checkSummary by CodeRabbit
@coderabbitai resolvecommand for CodeRabbit when applicable.