docs: fix stale plugin counts across documentation files#184
Conversation
Updated outdated numbers to match actual repository state: - ARCHITECTURE_PLAN.md: 5,047→5,046 plugins, 4,000+→5,000+ tools, 1,174→807 short descriptions - PLUGIN_STANDARDS.md: 1,179+→5,000+ plugins - ROADMAP.md: 1,269→5,000+ plugins, 1.3K+→5,000+ references - AGENTS.md: ~5,047→~5,046 plugins, ~1,176→~807 short descriptions - QUALITY_REPORT.md: 5,047→5,046 plugins scanned These numbers had drifted from reality as the plugin collection grew. Accurate counts help contributors understand the project's current scope and avoid confusion when cross-referencing documentation.
|
Warning Review limit reached
More reviews will be available in 41 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, 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 include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (5)
✨ 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 |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
Automated maintenance run by automaintainer.
Focus: Improve supercli static documentation: README, CONTRIBUTING, or docs/ files. Make ONE atomic commit with clear summary explaining what documentation was improved and WHY. Use fix:/docs: prefix. Keep it focused and reviewable.
Branch:
am/am-f17c27-tg5nrm