feat(cli): add built-in kilo-config skill - #7603
Merged
Merged
Conversation
Contributor
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Files Reviewed (2 files)
Reviewed by gpt-5.4-20260305 · 983,421 tokens |
The agent had no knowledge of ctrl+p commands, themes, or appearance toggling, so it told users to change their terminal settings instead. Add a TUI Settings section covering all command palette actions, keybinds, and slash commands, and widen the skill description to trigger on settings/appearance questions.
jeanduplessis
approved these changes
Mar 27, 2026
slamj1
pushed a commit
to slamj1/kilocode
that referenced
this pull request
May 16, 2026
jliounis
pushed a commit
to jliounis/kilocode
that referenced
this pull request
May 18, 2026
jliounis
pushed a commit
to jliounis/kilocode
that referenced
this pull request
May 18, 2026
feat(cli): add built-in kilo-config skill
t7tran
pushed a commit
to t7tran/kilocode
that referenced
this pull request
Aug 14, 2026
t7tran
pushed a commit
to t7tran/kilocode
that referenced
this pull request
Aug 14, 2026
feat(cli): add built-in kilo-config skill
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.
Followup to #7573
Why
When users ask about configuring Kilo, the agent has to fetch docs from the web, which is slow and unreliable. We need the configuration reference available instantly without burning system prompt tokens on every request.
Additionally, users asking the agent to change TUI settings (e.g. "toggle dark mode", "switch theme") got incorrect answers because the agent had no knowledge of the ctrl+p command palette, keybinds, or slash commands.
What changed
Added a built-in skill called
kilo-configthat ships inside the CLI binary. It contains a dense reference covering all configuration surfaces: commands, agents, permissions, MCP servers, providers, skills, plugins, and everykilo.jsonfield. The skill is registered at the lowest precedence before all filesystem discovery, so any user-defined skill with the same name cleanly overrides it. The skill tool now handles built-in skills without trying to list files or resolve filesystem paths. The cost is about 60 tokens per request for the skill listing, with the full ~1,500 token reference loaded on-demand only when relevant.The skill now also includes a TUI Settings section documenting all ctrl+p command palette actions, keybinds, and slash commands — covering themes, dark/light appearance toggle, session management, agent/model switching, and display toggles. The skill description was widened so the agent loads it when users ask about changing settings or appearance, not just
kilo.jsonconfig. The section explicitly notes that these are user-interactive only and the agent should direct users to the right command rather than trying to change settings itself.Demo
Look for
Skill "kilo-config":When asking for things that CLI cannot control yet:
How to test
bun run typecheckfrompackages/opencode/— should pass cleankilo-configskill instead of fetching web docs