Sharpen CodeTruss skill discovery#1
Conversation
|
Warning Review limit reached
Next review available in: 56 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: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThe release updates package and plugin versions to 0.1.1 and revises descriptions across manifests, skills, agent metadata, README marketplace notes, and Claude/OpenAI submission drafts. Changes0.1.1 release metadata
Estimated code review effort: 2 (Simple) | ~10 minutes 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (4 passed)
✨ 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 |
What changed
Why
Agent-skill discovery is driven primarily by the skill description. Generic “code review” is crowded, while CodeTruss owns a narrower task-contract problem. The metadata should trigger on the user language the product actually solves and should remain honest about owned-marketplace availability versus official directory approval.
Validation
npm testclaude plugin validate ./plugins/codetruss-claudeclaude plugin validate .git diff --checkNo MCP server, plugin-bundled hook, background service, automatic upload, or provider-consent behavior was added.
Summary by CodeRabbit