feat(skills): /feature non-interactive invocation support#3962
Conversation
…TOP instead of prompts When an orchestrating agent invokes /feature #N headlessly, collision, gh-failure, closed-issue, aged-scope and plan-validation waits emit structured SKIP:/STOP: lines instead of prompting, with claim rollback on post-claim stops. Interactive sessions unchanged. Closes #3959
|
Warning Review limit reached
Next review available in: 52 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: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ 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 |
1 participant
What
Adds Phase 0.0 §4b — a non-interactive contract for orchestrated (headless) invocations of
/feature #N: every STOP-and-ask becomes a structured final line (SKIP: collision — …,STOP: claim|freshness|scope — …), plan validation is satisfied by a pre-validated issue body, and a post-claim stop rolls the claim back. Interactive behavior is unchanged.Why
An orchestrating agent draining a queue cannot answer y/N prompts; without this contract a headless run stalls on the first collision or validation wait.
Closes #3959
https://claude.ai/code/session_01AMJQcgjxqkmLjtNSQmbm1S