docs: clarify slash commands (/newtask vs /smol) (#2160)#5869
Conversation
|
Review: kilocode #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 #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 |
Mirror: docs: clarify slash commands /newtask vs /smol (Kilo-Org#5869)
olearycrew
left a comment
olearycrew
left a comment
There was a problem hiding this comment.
@EloiRamos thanks for this!
4 participants
Context
Users have reported confusion between the
/newtaskand/smolslash commands (issue #2160). The existing documentation did not clearly explain the difference between these commands or when each should be used.Implementation
/newtaskand/smolto the Using Modes page./newtaskcreates a new task while carrying over context./smolcondenses the current context window.Behavior was verified against:
webview-ui/src/utils/slash-commands.tssrc/core/slash-commands/kilo.tssrc/core/prompts/commands.tsDocs-only change. No runtime code modified.
Fixes #2160