Skip to content

chore: trim package keywords to 8 - #40

Merged
IamCoder18 merged 2 commits into
mainfrom
chore/trim-package-keywords
Aug 10, 2026
Merged

chore: trim package keywords to 8#40
IamCoder18 merged 2 commits into
mainfrom
chore/trim-package-keywords

Conversation

@IamCoder18

Copy link
Copy Markdown
Owner

Reduces packages/cli/package.json keywords 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 to skill

Final keywords: huly, huly-cli, cli, ai-agent, self-hosted, issue-tracker, skill, openclaw

@coderabbitai

coderabbitai Bot commented Aug 10, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

Warning

Review limit reached

@IamCoder18, you've reached your PR review limit, so we couldn't start this review.

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 @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: dee1cc2f-1d99-43e5-b12a-3f4a6427cba9

📥 Commits

Reviewing files that changed from the base of the PR and between 5a48c33 and e9261da.

📒 Files selected for processing (1)
  • packages/cli/package.json
📝 Walkthrough

Walkthrough

The 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.

Changes

CLI package metadata

Layer / File(s) Summary
Update CLI package keywords
packages/cli/package.json
The keyword list removes API and MCP-related terms and includes CLI-focused keywords such as cli, ai-agent, self-hosted, issue-tracker, skill, and openclaw.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

Suggested reviewers: slegarraga

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly summarizes the main change: reducing package keywords to eight.
Description check ✅ Passed The description directly explains the keyword reduction, removed terms, and final keyword list.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches 💡 1
⚔️ Resolve merge conflicts 💡
  • Resolve merge conflict in branch chore/trim-package-keywords
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/trim-package-keywords

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@IamCoder18
IamCoder18 merged commit bf6997f into main Aug 10, 2026
1 of 3 checks passed
Comment thread packages/cli/package.json
"project-management",
"self-hosted"
"skill",
"openclaw"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

@kilo-code-bot

kilo-code-bot Bot commented Aug 10, 2026

Copy link
Copy Markdown

Code Review Summary

Status: 1 Issue Found | Recommendation: Address before merge

Overview

Severity Count
CRITICAL 0
WARNING 1
SUGGESTION 0
Issue Details (click to expand)

WARNING

File Line Issue
packages/cli/package.json 13 openclaw brand keyword placed at end while other brand keywords (huly, huly-cli) are at the top — inconsistent grouping and reduces discoverability on the npm registry page, which renders keywords in array order.
Files Reviewed (1 file)
  • packages/cli/package.json - 1 issue

Fix these issues in Kilo Cloud


Reviewed by minimax-m3 · Input: 26.9K · Output: 14K · Cached: 487.6K

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant