Skip to content

docs: drop stale kimi KIMI.md->AGENTS.md migration note#3291

Open
Quratulain-bilal wants to merge 1 commit into
github:mainfrom
Quratulain-bilal:docs/kimi-drop-stale-agent-context
Open

docs: drop stale kimi KIMI.md->AGENTS.md migration note#3291
Quratulain-bilal wants to merge 1 commit into
github:mainfrom
Quratulain-bilal:docs/kimi-drop-stale-agent-context

Conversation

@Quratulain-bilal

Copy link
Copy Markdown
Contributor

closes #3290

#3097 ("make agent-context extension a full opt-in", v0.12.0) removed the KIMI.md -> AGENTS.md context migration from the kimi integration — _migrate_legacy_kimi_context_file and the context_file = "AGENTS.md" handling were deleted. --migrate-legacy now only moves the skills directory.

two lines in docs/reference/integrations.md still promised the removed migration (the kimi row in the supported-agents table and the kimi --migrate-legacy row in the integration-specific options table). this drops that clause from both so the docs match the code.

docs-only, no code touched. verified against the merged #3097 diff (the removed context_file/_migrate_legacy_kimi_context_file lines) and the current src/specify_cli/integrations/kimi/__init__.py (skills-dir migration only).


note: i used an ai assistant to help investigate and write this up.

github#3097 made the agent-context extension a full opt-in and removed the
KIMI.md -> AGENTS.md context migration from the kimi integration
(_migrate_legacy_kimi_context_file and the context_file handling are
gone). kimi's --migrate-legacy now only moves the skills directory. two
lines in the integrations reference still promised the removed context
migration; drop that clause so the docs match the code.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

Updates the integrations reference documentation to remove stale claims about kimi migrating KIMI.mdAGENTS.md, aligning docs with the post-#3097 behavior where --migrate-legacy only migrates legacy skills installs.

Changes:

  • Removed the KIMI.mdAGENTS.md migration clause from the Kimi entry in the supported agents table.
  • Removed the same clause from the kimi --migrate-legacy integration-specific options entry.
Show a summary per file
File Description
docs/reference/integrations.md Removes outdated Kimi context-migration wording from two documentation tables.

Review details

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

  • Files reviewed: 1/1 changed files
  • Comments generated: 1
  • Review effort level: Low

| ----------- | ------------------- | -------------------------------------------------------------- |
| `generic` | `--commands-dir` | Required. Directory for command files |
| `kimi` | `--migrate-legacy` | Migrate legacy `.kimi/skills/` installs to `.kimi-code/skills/` (including dotted→hyphenated directory names); when the `agent-context` extension is enabled, also migrates `KIMI.md` to `AGENTS.md` |
| `kimi` | `--migrate-legacy` | Migrate legacy `.kimi/skills/` installs to `.kimi-code/skills/` (including dotted→hyphenated directory names) |
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.

Docs: kimi --migrate-legacy still documents the KIMI.md -> AGENTS.md migration removed in #3097

3 participants