update Kimi CLI to Kimi Code

[akeyz]

Kimi official code is now Kimi Code. The project detect folder has changed from .kimi to .kimi-code.

https://www.kimi.com/code

Summary by CodeRabbit

• Documentation
  • Updated command syntax and supported tools content to use Kimi Code, including skill-based command patterns and the note that it does not use generated opsx-* command files.
• Chores
  • Renamed the Kimi integration label to Kimi Code and switched the managed skills directory to .kimi-code (with legacy detection for .kimi).
• Bug Fixes
  • Added legacy skill-directory migration during both init and update, moving managed skills from .kimi to .kimi-code while preserving user-owned files.
• Tests
  • Updated and expanded init/update coverage to verify the migration behavior and expected filesystem outcomes.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: e5125300-6bfe-49e9-b9d7-89c5824e1fc5

📥 Commits

Reviewing files that changed from the base of the PR and between d05aa90 and d532adc.

📒 Files selected for processing (8)

• openspec/specs/ai-tool-paths/spec.md
• openspec/specs/cli-init/spec.md
• src/core/config.ts
• src/core/init.ts
• src/core/migration.ts
• src/core/update.ts
• test/core/init.test.ts
• test/core/update.test.ts

🚧 Files skipped from review as they are similar to previous changes (1)

• src/core/config.ts

---

📝 Walkthrough

Walkthrough

The PR renames the Kimi integration to “Kimi Code”, changes managed skills from .kimi to .kimi-code, and adds legacy skill migration during initialization and updates while preserving user files.

Changes

Kimi Code configuration and migration

Layer / File(s)	Summary
Kimi Code paths and specifications src/core/config.ts, docs/supported-tools.md, docs/commands.md, openspec/specs/...	Kimi uses .kimi-code for managed skills, recognizes both current and legacy paths, and documents skill-based commands without generated command files.
Legacy skill migration src/core/migration.ts	Managed workflow skill directories are moved from .kimi/skills to .kimi-code/skills; existing destinations are removed from the legacy location, while non-empty legacy directories are preserved.
Init/update integration and tests src/core/init.ts, src/core/update.ts, test/core/...	Init and update run migration before subsequent setup, log update migrations, and test managed-skill movement, cleanup, and preservation of user files.

Estimated code review effort: 3 (Moderate) | ~25 minutes

Sequence Diagram(s)

sequenceDiagram
  participant InitUpdate
  participant migrateLegacySkillDirs
  participant FileSystem
  InitUpdate->>migrateLegacySkillDirs: migrate project skill directories
  migrateLegacySkillDirs->>FileSystem: inspect legacy .kimi/skills workflows
  migrateLegacySkillDirs->>FileSystem: move managed workflows to .kimi-code/skills
  migrateLegacySkillDirs->>FileSystem: preserve user files and remove empty directories
  migrateLegacySkillDirs-->>InitUpdate: return migration records

Loading

Possibly related PRs

• Fission-AI/OpenSpec#1003: Extends the earlier Kimi CLI skills-only support by renaming its managed skills directory and adding init/update migration.

Suggested reviewers: tabishb

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately captures the main rename from Kimi CLI to Kimi Code and is concise.
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

🧪 Generate unit tests (beta)

• Create PR with unit tests

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

ESLint install timed out. The project may have too many dependencies for the sandbox.

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/commands.md`:
- Around line 675-677: Update the command reference table to remove the stale
Kimi CLI row, then consolidate the duplicate Trae entries into one authoritative
Trae row using the correct invocation syntax. Preserve the surrounding table
structure and other tool entries.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: fd9778c9-b4b0-4942-b5ae-d338837aff7d

📥 Commits

Reviewing files that changed from the base of the PR and between ba0a38c and d8cd91a.

📒 Files selected for processing (3)

• docs/commands.md
• docs/supported-tools.md
• src/core/config.ts

🚧 Files skipped from review as they are similar to previous changes (2)

• src/core/config.ts
• docs/supported-tools.md

[alfred-openspec]

Changing skillsDir strands OpenSpec-managed .kimi/skills files because update and cleanup only inspect current AI_TOOLS paths. Please add legacy cleanup or migration for managed OpenSpec skills, preserving user files, with a focused update test before moving generation to the current .kimi-code/skills path.

[clay-good]

Pushed e8ad256 addressing @alfred-openspec's review:

• Legacy migration: new migrateLegacySkillDirs in src/core/migration.ts with a LEGACY_SKILLS_DIRS map (kimi: ['.kimi']). Both openspec init and openspec update run it before tool detection: OpenSpec-managed openspec-* skill directories are moved from .kimi/skills to .kimi-code/skills (or dropped if the destination already exists), so old installs stay detected and get refreshed instead of being stranded.
• User files preserved: only known openspec-* skill dirs containing a SKILL.md are touched; .kimi/skills and .kimi are removed only when left empty. .kimi also remains a detection path so existing Kimi projects are still recognized.
• Focused tests: update test covering migrate + refresh + user-file preservation, an empty-legacy-dir removal test, and an init migration test.
• Spec scenario for kimi updated to .kimi-code (it still said .kimi).

Verified end-to-end with the built CLI: a project with legacy .kimi/skills/openspec-explore plus user files prints Migrated 1 skill directory: .kimi/skills → .kimi-code/skills, regenerates all core skills under .kimi-code, and leaves the user's files in .kimi untouched.

[alfred-openspec]

The migration now preserves legacy detection, moves known OpenSpec workflow directories before init and update, retains sibling user skills and config, and removes old roots only when empty. The current .kimi-code path matches official Kimi Code docs, focused lifecycle tests pass, and full CI is green.