docs: refactor CLI command docs to eliminate redundancy

Streamlined 7 CLI command documentation files by removing duplicate content that's already comprehensively covered in intelligent-tools-strategy.md (loaded in memory). Established single source of truth (SSOT) pattern. Changes: - Removed duplicate command templates (→ strategy lines 51-118) - Removed file pattern reference lists (→ strategy lines 324-329) - Removed complex pattern discovery steps (→ strategy lines 331-355) - Removed MODE field definitions (→ strategy lines 128-143) - Removed tool feature descriptions (→ strategy lines 283-322) Files streamlined: - analyze.md: 117→61 lines (48% reduction) - chat.md: 118→62 lines (47% reduction) - execute.md: 180→100 lines (44% reduction) - codex-execute.md: 481→473 lines (2% - preserved unique content) - mode/bug-index.md: 144→75 lines (48% reduction) - mode/code-analysis.md: 188→76 lines (60% reduction) - mode/plan.md: 100→76 lines (24% reduction) Total reduction: 681 lines removed across all files Each doc now contains only: - Unique purpose and parameters - Command-specific execution flow - Practical examples - Brief reference to intelligent-tools-strategy.md 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
2026-02-13 02:41:50 +08:00 · 2025-10-05 10:35:27 +08:00
parent a9d6de228e
commit 467963eee2
7 changed files with 203 additions and 690 deletions
--- a/.claude/commands/cli/mode/bug-index.md
+++ b/.claude/commands/cli/mode/bug-index.md
@@ -14,131 +14,61 @@ allowed-tools: SlashCommand(*), Bash(*)

 ## Purpose

-Execute systematic bug analysis and fix suggestions using CLI tools with diagnostic template.
+Systematic bug analysis with diagnostic template (`~/.claude/prompt-templates/bug-fix.md`).

 **Supported Tools**: codex, gemini (default), qwen
+**Key Feature**: `--cd` flag for directory-scoped analysis
+
+## Parameters
+
+- `--tool <codex|gemini|qwen>` - Tool selection (default: gemini)
+- `--enhance` - Enhance bug description with `/enhance-prompt` first
+- `--cd "path"` - Target directory for focused analysis
+- `<bug-description>` (Required) - Bug description or error message

 ## Execution Flow

-1. **Parse tool selection**: Extract `--tool` flag (default: gemini)
-2. **If `--enhance` flag present**: Execute `/enhance-prompt "[bug-description]"` first
-3. Parse bug description (original or enhanced)
-4. Detect target directory (from `--cd` or auto-infer)
-5. Build command for selected tool with bug-fix template
-6. Execute analysis
-7. Save to session (if active)
+1. Parse tool and directory options
+2. If `--enhance`: Execute `/enhance-prompt` to expand bug context
+3. Use bug-fix template: `~/.claude/prompt-templates/bug-fix.md`
+4. Execute with `--all-files` in target directory
+5. Save to `.workflow/WFS-[id]/.chat/bug-index-[timestamp].md`

-## Core Rules
+## Analysis Focus (via Template)

-1. **Enhance First (if flagged)**: Execute `/enhance-prompt` before analysis
-2. **Directory Context**: Use `cd` when `--cd` provided or auto-detected
-3. **Template Required**: Always use bug-fix template
-4. **Session Output**: Save to `.workflow/WFS-[id]/.chat/bug-index-[timestamp].md`
-
-## Command Template
-
-```bash
-cd [directory] && ~/.claude/scripts/gemini-wrapper --all-files -p "
-PURPOSE: [bug analysis goal]
-TASK: Systematic bug analysis and fix recommendations
-CONTEXT: @{CLAUDE.md,**/*CLAUDE.md} [entire codebase in directory]
-EXPECTED: Root cause analysis, code path tracing, targeted fixes
-RULES: $(cat ~/.claude/prompt-templates/bug-fix.md) | Bug: [description]
-"
-```
+- Root cause investigation
+- Code path tracing
+- Targeted minimal fixes
+- Impact assessment

 ## Examples

-**Basic Bug Analysis**:
 ```bash
-cd . && ~/.claude/scripts/gemini-wrapper --all-files -p "
-PURPOSE: Debug authentication null pointer error
-TASK: Identify root cause and provide fix
-CONTEXT: @{CLAUDE.md,**/*CLAUDE.md}
-EXPECTED: Root cause, code path, minimal fix, impact assessment
-RULES: $(cat ~/.claude/prompt-templates/bug-fix.md) | Bug: null pointer in login flow
-"
+# Basic bug analysis
+/cli:mode:bug-index "null pointer in authentication"
+
+# Directory-specific
+/cli:mode:bug-index --cd "src/auth" "token validation fails"
+
+# Enhanced description
+/cli:mode:bug-index --enhance "login broken"
+
+# Qwen for architecture-related bugs
+/cli:mode:bug-index --tool qwen "circular dependency in modules"
 ```

-**Directory-Specific**:
-```bash
-cd src/auth && ~/.claude/scripts/gemini-wrapper --all-files -p "
-PURPOSE: Fix token validation failure
-TASK: Analyze token validation bug in auth module
-CONTEXT: @{CLAUDE.md,**/*CLAUDE.md}
-EXPECTED: Validation logic analysis, fix recommendation
-RULES: $(cat ~/.claude/prompt-templates/bug-fix.md) | Bug: token validation fails intermittently
-"
-```
-
-**With Enhancement**:
-```bash
-# User: /gemini:mode:bug-index --enhance "login broken"
-
-# Step 1: Enhance
-/enhance-prompt "login broken"
-# Returns:
-# INTENT: Debug login authentication failure
-# CONTEXT: Known session state issue
-# ACTION: Check session management → verify token → test flow
-
-# Step 2: Analyze with enhanced context
-cd . && ~/.claude/scripts/gemini-wrapper --all-files -p "
-PURPOSE: Debug login authentication failure
-TASK: Analyze session management, token handling, auth flow
-CONTEXT: @{CLAUDE.md,**/*CLAUDE.md} Known: session state issue
-EXPECTED: Root cause in session/token, targeted fix
-RULES: $(cat ~/.claude/prompt-templates/bug-fix.md) | Focus on session management
-"
-```
-
-## Analysis Focus
-
-**Template provides**:
- **Root Cause Analysis**: Systematic investigation
- **Code Path Tracing**: Execution flow analysis
- **Targeted Solutions**: Minimal, specific fixes
- **Impact Assessment**: Side effect evaluation
-
-## File Pattern Reference
-
-### Common Patterns
- All files: `@{**/*}`
- Source files: `@{src/**/*}`
- TypeScript: `@{*.ts,*.tsx}`
- JavaScript: `@{*.js,*.jsx}`
- Python: `@{*.py}`
- With docs: `@{CLAUDE.md,**/*CLAUDE.md}`
- Tests: `@{**/*.test.*,**/*.spec.*}`
-
-### Complex Pattern Discovery
-For bug investigation, use semantic discovery to find relevant code:
+## Bug Investigation Workflow

 ```bash
-# Step 1: Find bug-related files
-rg "error_keyword|exception_pattern" --files-with-matches
-mcp__code-index__search_code_advanced(pattern="throw|catch|error", file_pattern="*.ts")
+# 1. Find bug-related files
+rg "error_keyword" --files-with-matches

-# Step 2: Trace error propagation path
-# Identify: origin → propagation → handler
-
-# Step 3: Execute bug analysis with focused context
-cd src && ~/.claude/scripts/gemini-wrapper --all-files -p "
-PURPOSE: Debug null pointer error in authentication
-TASK: Identify root cause and provide fix
-MODE: analysis
-CONTEXT: @{CLAUDE.md,auth/service.ts,middleware/auth.ts}
-EXPECTED: Root cause, execution trace, minimal fix
-RULES: $(cat ~/.claude/prompt-templates/bug-fix.md) | Bug: null pointer in token validation
-"
+# 2. Execute bug analysis with focused context
+/cli:mode:bug-index --cd "src/module" "specific error description"
 ```

-## Session Output
+## Notes

-**Location**: `.workflow/WFS-[topic]/.chat/bug-index-[timestamp].md`
-
-**Includes**:
- Bug description
- Template used
- Analysis results
- Recommended actions
+- Command templates and file patterns: see intelligent-tools-strategy.md (loaded in memory)
+- Template path: `~/.claude/prompt-templates/bug-fix.md`
+- Always uses `--all-files` for comprehensive codebase context