feat(agents): add /aikido-weekly-review command for recurring feed reviews - #2163
Conversation
…views Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
Warning Review limit reached
Next review available in: 3 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: Repository UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (4)
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 |
…kly review Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
@coderabbitai review |
✅ Action performedReview finished.
|
…ion group Findings are grouped into decision-sized units (deps by package, SAST by rule x file-family, actions by rule); the command presents a suggested action per group and executes only what the user accepts, optionally as one task chip per group. Leaked secrets stay individually escalated. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…keting Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Which Linear task belongs to this PR?
Fixes EXSC-733
Why did I implement it this way?
Adds
/aikido-weekly-review— a cadence-review command any tech lead can run (or schedule) to review a repo's whole Aikido feed: pulls all open findings via the Aikido MCP with pagination, renders a severity×type dashboard with SLA state (out_of_sla/sla_due_soon), groups findings into decision-sized action groups (dependencies by package, SAST by rule × file-family, actions findings by rule), presents a suggested action per group, and executes ONLY what the user accepts — optionally spawning one background task chip per accepted group so each fix becomes its own session/PR. Leaked secrets are escalated individually and never grouped or ignorable. Ends by offering to schedule the next weekly run (scheduled task or calendar event).It deliberately orchestrates rather than duplicates: all triage mechanics, fix recipes, and the false-positive catalogue stay in
/aikido-address-findings(per the no-duplication rule in010-agents-authoring). Authored per/add-rule-or-skill: canonical file in.agents/commands/, symlinks for Cursor and Claude Code, README table updated.Checklist before requesting a review
Checklist for reviewer (DO NOT DEPLOY and contracts BEFORE CHECKING THIS!!!)