chore: trim package keywords to 8 - #40
Conversation
|
Warning Review limit reached
Next review available in: 57 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. 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: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe CLI package metadata updates its keywords. It removes API, MCP, SDK, client, headless, and project-management terms. It retains or adds CLI, AI-agent, self-hosted, issue-tracker, skill, and OpenClaw terms. ChangesCLI package metadata
Estimated code review effort: 1 (Trivial) | ~2 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches 💡 1⚔️ Resolve merge conflicts 💡
🧪 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 |
| "project-management", | ||
| "self-hosted" | ||
| "skill", | ||
| "openclaw" |
There was a problem hiding this comment.
WARNING: openclaw brand keyword placement is inconsistent with other brand keywords
The other brand identifiers (huly, huly-cli) are grouped at the top of the array, but openclaw — which appears to be the ClawHub distribution channel (see commit 18dd603 feat(publish): publish skill to ClawHub in lockstep with npm release and the clawhub config in scripts/) — is placed at the very end of the array, separated from the other brand keywords.
On the npm registry page, keywords are rendered in the order they appear in package.json, so a brand keyword placed last is the least discoverable. The current ordering looks like an incidental side effect of the diff (the deleted openclaw line was simply moved to a new trailing position) rather than an intentional categorization choice.
If openclaw is meant to be a brand keyword, consider moving it to position 3 (after huly-cli) so it sits alongside the other brand identifiers.
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
Code Review SummaryStatus: 1 Issue Found | Recommendation: Address before merge Overview
Issue Details (click to expand)WARNING
Files Reviewed (1 file)
Fix these issues in Kilo Cloud Reviewed by minimax-m3 · Input: 26.9K · Output: 14K · Cached: 487.6K |
Reduces
packages/cli/package.jsonkeywords from 15 to 8 to avoid keyword-stuffing flags from npm's algorithm.Removed:
huly-mcp,huly-api,huly-sdk,huly-client(variants of the brand)mcp-server,headless,project-management(redundant/generic)agent-skills→ renamed toskillFinal keywords:
huly,huly-cli,cli,ai-agent,self-hosted,issue-tracker,skill,openclaw