chore: delete label-driven dispatcher skills#50
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 (4)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Summary
Final cleanup of the label-convention strip. Deletes the 4 operator skills whose entire purpose was label-driven dispatch.
Changes
claude-code/.claude/skills/issue/SKILL.md— filed issues withtype:*/severity:*/stage:triagedlabels; without those, the skill is justgh issue createwith extra steps.claude-code/.claude/skills/merge/SKILL.md— filtered open PRs bystage:ready-for-merge; no label = no filter.claude-code/.claude/skills/run/SKILL.md— dispatched subagents perstage:*label; pure label-driven orchestration.claude-code/.claude/skills/unblock/SKILL.md— surfacedauto:requires-human/sensitivity:*items from/runreports (which no longer exist).Why
Layer-3 dispatcher is stopped, all label definitions deleted org-wide. These skills can be rebuilt cleanly alongside the new label schema if/when wanted.
🤖 Generated with Claude Code