feat: add skill discovery commands - #2780
Conversation
🦋 Changeset detectedLatest commit: 1dd712f The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 1dd712f670
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| host.showStatus(`Skill "${name}" is not slash-invocable.`, 'warning'); | ||
| return; | ||
| } | ||
| host.restoreInputText(`/${commandName} `); |
There was a problem hiding this comment.
Refresh skill commands before inserting from /skills
When the skill catalog changes after the last startup/session switch/reload (for example a new .kimi-code/skills/*/SKILL.md is added while the TUI is open), this picker reads the fresh inspectSkills() report but never updates host.skillCommandMap. Selecting that newly discovered skill inserts /skill:name, yet dispatchInput resolves skills only through the stale map, so pressing Enter sends the slash command as a normal model message instead of activating the skill. Refresh the host skill commands from this report/session before inserting, or activate through a path that does not depend on the cached map.
Useful? React with 👍 / 👎.
|
Thank you for your interest in contributing to Kimi Code. For new features, please discuss first. We are not currently accepting pull requests for new features. |
Related Issue
Resolve #60
Problem
Skills can currently be invoked through generated slash commands, but users have no supported way to inspect which Skill files were loaded, where they came from, what command name is effective, or why a Skill was skipped. This makes discovery and troubleshooting difficult in both the TUI and automation.
What changed
/skillspicker that displays the effective command, name, source, type, description, and path; selection inserts the command without executing it;kimi skills listandkimi skills list --jsonfor session-less workspace inspection, including support for the global--skills-diroverride;listSkillsandlistWorkspaceSkillsAPIs;Verification:
--skills-dir.Checklist
gen-changesetsskill, or this PR needs no changeset.gen-docsskill, or this PR needs no doc update.