chore: strip residual refs to deleted rules/commands from tooling-reference.md#51
Conversation
|
Warning Rate limit exceeded
To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Summary
Final residual cleanup. tooling-reference.md described skills/rules that were deleted in the org-wide label-convention strip earlier today, leaving stale doctrine pointers and dead command descriptions.
Changes (
.claude/rules/tooling-reference.md)pipeline-nevers.mdin the intro paragraph.## Operator commandssection — it described/run,/merge,/unblock,/issuewhich were deleted inOpen-Paws/structured-coding-with-ai#50.🤖 Generated with Claude Code