-
Notifications
You must be signed in to change notification settings - Fork 0
Mirror: docs: clarify slash commands /newtask vs /smol (#5869) #5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|
@@ -164,8 +164,13 @@ Review your code locally before pushing — catch issues early without waiting f | |||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||
| Configuration is managed through: | ||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||
| - `/connect` command for provider setup (interactive) | ||||||||||||||||||||||||||||||||||||
| - Config files directly at `~/.config/kilo/config.json` | ||||||||||||||||||||||||||||||||||||
| ## Slash Commands | ||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||
| The CLI's interactive mode supports slash commands for common operations. The main commands are documented above in the [Interactive Slash Commands](#interactive-slash-commands) section. | ||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||
| {% callout type="tip" %} | ||||||||||||||||||||||||||||||||||||
| **Confused about /newtask vs /smol in the IDE?** See the [Using Modes](/docs/code-with-ai/agents/using-modes#understanding-newtask-vs-smol) documentation for details. | ||||||||||||||||||||||||||||||||||||
| {% /callout %} | ||||||||||||||||||||||||||||||||||||
|
Comment on lines
+167
to
+173
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The new 'Slash Commands' header is placed immediately after the 'Configuration is managed through:' sentence, which breaks the grammatical flow and orphans the subsequent list items. Additionally, the reference to the config file location (
Suggested change
|
||||||||||||||||||||||||||||||||||||
| - `kilo auth` for credential management | ||||||||||||||||||||||||||||||||||||
|
Comment on lines
+167
to
174
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Fix document structure: orphaned bullet point. The new "Slash Commands" section is clear and helpful, but it creates a structural issue. Line 165 says "Configuration is managed through:" which suggests a list should follow, but instead there's a peer-level section header (## Slash Commands), and then a single orphaned bullet point at line 174. Consider one of these solutions:
📝 Proposed fix: Move the bullet point before the new section Configuration is managed through:
+- `kilo auth` for credential management
+
## Slash Commands
The CLI's interactive mode supports slash commands for common operations. The main commands are documented above in the [Interactive Slash Commands](`#interactive-slash-commands`) section.
{% callout type="tip" %}
**Confused about /newtask vs /smol in the IDE?** See the [Using Modes](/docs/code-with-ai/agents/using-modes#understanding-newtask-vs-smol) documentation for details.
{% /callout %}
-- `kilo auth` for credential management🤖 Prompt for AI Agents |
||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||
| ## Permissions | ||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Inserting a level-3 header (
###) inside a numbered list breaks the list's continuity in most Markdown parsers. This will cause the subsequent list item (currently step 3) to restart its numbering at '1.' or render incorrectly. To maintain the list structure, you should indent this explanatory section so it remains part of step 2.