Mirror: docs: clarify slash commands /newtask vs /smol (#5869)#5
Conversation
Summary of ChangesHello @jeremylongshore, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request enhances the clarity of the documentation by specifically addressing common confusion between the Highlights
Changelog
Activity
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
📝 WalkthroughWalkthroughDocumentation files have been expanded to provide clearer guidance on slash commands and agent modes, introducing new comparison tables and dedicated sections to explain command purposes and functionality. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 2❌ Failed checks (2 warnings)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches🧪 Generate unit tests (beta)
⚔️ Resolve merge conflicts (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Failed to generate code suggestions for PR |
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
The documentation changes provide helpful clarification on the /newtask and /smol commands. However, there are some formatting and structural issues: a header inserted within a numbered list in using-modes.md breaks the list continuity, and the placement of a new section in cli.md disrupts the existing 'Configuration' section and accidentally removes useful information about config file locations.
| ### Understanding /newtask vs /smol | ||
|
|
||
| Users often confuse `/newtask` and `/smol`. Here's the key difference: | ||
|
|
||
| | Command | Purpose | When to Use | | ||
| | ---------- | ----------------------------------------------------- | ----------------------------------------------------------------------- | | ||
| | `/newtask` | Creates a new task with context from the current task | When you want to start something new while carrying over context | | ||
| | `/smol` | Condenses your current context window | When your conversation is getting too long and you want to summarize it | |
There was a problem hiding this comment.
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.
| ### Understanding /newtask vs /smol | |
| Users often confuse `/newtask` and `/smol`. Here's the key difference: | |
| | Command | Purpose | When to Use | | |
| | ---------- | ----------------------------------------------------- | ----------------------------------------------------------------------- | | |
| | `/newtask` | Creates a new task with context from the current task | When you want to start something new while carrying over context | | |
| | `/smol` | Condenses your current context window | When your conversation is getting too long and you want to summarize it | | |
| ### Understanding /newtask vs /smol | |
| Users often confuse `/newtask` and `/smol`. Here's the key difference: | |
| | Command | Purpose | When to Use | | |
| | ---------- | ----------------------------------------------------- | ----------------------------------------------------------------------- | | |
| | `/newtask` | Creates a new task with context from the current task | When you want to start something new while carrying over context | | |
| | `/smol` | Condenses your current context window | When your conversation is getting too long and you want to summarize it | |
| ## 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 %} |
There was a problem hiding this comment.
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 (~/.config/kilo/config.json) was removed. It is better to keep the configuration list intact and place the new section separately.
| ## 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 %} | |
| - `/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 %} |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In `@apps/kilocode-docs/pages/code-with-ai/platforms/cli.md`:
- Around line 167-174: The document has an orphaned bullet "kilo auth" that
follows the sentence "Configuration is managed through:" but sits after the new
"## Slash Commands" header; move the `kilo auth` bullet so it appears
immediately after the "Configuration is managed through:" sentence (i.e., before
the "## Slash Commands" section) to make the list structurally correct, keeping
the "## Slash Commands" section and its callout unchanged.
🧹 Nitpick comments (1)
apps/kilocode-docs/pages/code-with-ai/agents/using-modes.md (1)
31-38: Excellent addition with minor style suggestion.The new subsection effectively clarifies the distinction between
/newtaskand/smolwith a clear comparison table. The content is accurate and addresses the confusion mentioned in the PR objectives.Minor style suggestion: The "When to Use" column uses "want to" twice (lines 37 and 38). Consider varying the phrasing for smoother reading:
✍️ Optional style refinement
| Command | Purpose | When to Use | | ---------- | ----------------------------------------------------- | ----------------------------------------------------------------------- | -| `/newtask` | Creates a new task with context from the current task | When you want to start something new while carrying over context | -| `/smol` | Condenses your current context window | When your conversation is getting too long and you want to summarize it | +| `/newtask` | Creates a new task with context from the current task | When starting something new while carrying over context | +| `/smol` | Condenses your current context window | When your conversation is getting too long and needs summarizing |
| ## 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 |
There was a problem hiding this comment.
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:
- Move the
kilo authbullet point before the new Slash Commands section (after line 165) - Convert line 174 to a regular paragraph without the bullet
- Update line 165 to not imply a list follows
📝 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
In `@apps/kilocode-docs/pages/code-with-ai/platforms/cli.md` around lines 167 -
174, The document has an orphaned bullet "kilo auth" that follows the sentence
"Configuration is managed through:" but sits after the new "## Slash Commands"
header; move the `kilo auth` bullet so it appears immediately after the
"Configuration is managed through:" sentence (i.e., before the "## Slash
Commands" section) to make the list structurally correct, keeping the "## Slash
Commands" section and its callout unchanged.
jeremylongshore
force-pushed
the
main
branch
from
4231140 to
fa13626
Compare
Review: kilocode Kilo-Org#5869
Checklist
Findings🟡 cli.md: New section breaks existing configuration listFile: The new
Before: Configuration is managed through:
- `/connect` command for provider setup (interactive)
- Config files directly at `~/.config/kilo/config.json`
- `kilo auth` for credential managementAfter (problematic): Configuration is managed through:
## Slash Commands
...
{% /callout %}
- `kilo auth` for credential managementSuggested fix: Keep the configuration list intact. Place the new Slash Commands section either before or after the Configuration block, and restore the removed list items. ✅ using-modes.md: Clean and accurateThe additions to CI Status
Code Snippets# apps/kilocode-docs/pages/code-with-ai/platforms/cli.md (structural issue)
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...
+
+{% callout type="tip" %}
+**Confused about /newtask vs /smol in the IDE?**...
+{% /callout %}
- `kilo auth` for credential management# apps/kilocode-docs/pages/code-with-ai/agents/using-modes.md (clean)
-2. **Slash command:** Type `/architect`, `/ask`, `/debug`, or `/code` in the chat input
+2. **Slash command:** Type `/architect`, `/ask`, `/debug`, or `/code` in the chat input to switch modes. Type `/newtask` to create a new task, or `/smol` to condense your context window.
+### Understanding /newtask vs /smol
+
+| Command | Purpose | When to Use |
+| ---------- | ----------------------------------------------------- | ------------------------------------------------ |
+| `/newtask` | Creates a new task with context from the current task | When you want to start something new... |
+| `/smol` | Condenses your current context window | When your conversation is getting too long... |VerdictCOMMENT - The |
Review Journal: kilocode Kilo-Org#5869
SummaryThis PR addresses issue #2160 by clarifying the difference between First ImpressionsA What I Looked At
Analysisusing-modes.md — CleanThe change extends step 2 in the "Four ways to switch modes" list and adds a subsection with a comparison table:
I verified these descriptions against the source code: // webview-ui/src/utils/slash-commands.ts
{ name: "newtask", description: "Create a new task with context from the current task" },
{ name: "smol", description: "Condenses your current context window" },Accurate match. The cli.md — Structural BreakThe new
The intent is good — adding a cross-reference to the using-modes.md explanation. But the execution needs restructuring: keep the configuration list intact and place the Slash Commands section in its own location. VerificationAll relevant CI checks pass: Diagramsgraph LR
subgraph "using-modes.md ✅"
A["Step 2: Slash command"] --> B["Extended text<br>/newtask, /smol mentioned"]
B --> C["NEW: ### Understanding<br>/newtask vs /smol"]
C --> D["Comparison table"]
end
subgraph "cli.md ⚠️"
E["'Configuration is<br>managed through:'"] --> F["❌ /connect removed"]
E --> G["❌ config path removed"]
E --> H["NEW: ## Slash Commands<br>(breaks list)"]
H --> I["Tip callout<br>(cross-ref to using-modes)"]
I --> J["⚠️ Orphaned:<br>'kilo auth'"]
end
style C fill:#2d6a4f,stroke:#1b4332,color:#d8f3dc
style D fill:#2d6a4f,stroke:#1b4332,color:#d8f3dc
style F fill:#9d0208,stroke:#6a040f,color:#fff
style G fill:#9d0208,stroke:#6a040f,color:#fff
style H fill:#e9c46a,stroke:#f4a261,color:#264653
style J fill:#e9c46a,stroke:#f4a261,color:#264653
Bot Review Synthesis
Bot consensus: CodeRabbit and Gemini both independently identified the cli.md structural issue. Gemini also flagged the Lessons Learned1. Cross-cutting docs changes need structural awareness. When adding content to existing documentation, check that you're not splitting an in-progress syntactic structure (list, table, code block). The cli.md change is a classic "insert in the wrong spot" issue. 2. Bot agreement strengthens review confidence. When two independent AI reviewers flag the same issue with different framing (CodeRabbit: "orphaned bullet", Gemini: "breaks grammatical flow"), the finding is almost certainly real. This is the first review where bot consensus directly validated manual analysis. 3. Source code verification catches docs drift. Checking slash command descriptions against 4. All CI green doesn't mean all content is correct. Markdoc built successfully despite the structural issue. The build validates syntax, not document coherence. Human/AI review catches what CI cannot. Review #2 of 75 | Review methodology: AI PR Review Case Studies | Reviewed with GWI + Claude Code |
2 participants
Mirror of Kilo-Org#5869
This PR mirrors the upstream change for multi-AI review analysis.
Original Description
Clarifies the difference between
/newtaskand/smolslash commands. Adds comparison table to Using Modes page and cross-reference in CLI docs. Fixes Kilo-Org#2160.Bot Review Tracker
Links
Summary by CodeRabbit
Documentation
/newtaskand/smolcommands