docs: drop stale kimi KIMI.md->AGENTS.md migration note#3291
Merged
mnriem merged 2 commits intoJul 2, 2026
Conversation
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.
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the integrations reference documentation to remove stale claims about kimi migrating KIMI.md → AGENTS.md, aligning docs with the post-#3097 behavior where --migrate-legacy only migrates legacy skills installs.
Changes:
- Removed the
KIMI.md→AGENTS.mdmigration clause from the Kimi entry in the supported agents table. - Removed the same clause from the
kimi --migrate-legacyintegration-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
Collaborator
|
Please address Copilot feedback. If not applicable or wrong, please explain why |
address review: the parenthetical said 'dotted->hyphenated directory names', but the migration is about skill naming (speckit.xxx -> speckit-xxx), matching the module docstring. reword to match.
Contributor
Author
|
addressed in 691490e. copilot is right: the migration is about skill naming (speckit.xxx -> speckit-xxx), which is also how the module docstring describes it. reworded 'directory names' to 'skill naming' and added the speckit.xxx -> speckit-xxx example. |
mnriem
approved these changes
Jul 2, 2026
Collaborator
|
Thank you! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
closes #3290
#3097 ("make agent-context extension a full opt-in", v0.12.0) removed the
KIMI.md->AGENTS.mdcontext migration from the kimi integration —_migrate_legacy_kimi_context_fileand thecontext_file = "AGENTS.md"handling were deleted.--migrate-legacynow only moves the skills directory.two lines in
docs/reference/integrations.mdstill promised the removed migration (the kimi row in the supported-agents table and the kimi--migrate-legacyrow 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_filelines) and the currentsrc/specify_cli/integrations/kimi/__init__.py(skills-dir migration only).note: i used an ai assistant to help investigate and write this up.