mirror of https://github.com/catlog22/Claude-Code-Workflow.git synced 2026-02-10 02:24:35 +08:00

Files

catlog22 369bfa8a08 Refactor command YAML headers: replace examples with argument-hint

**Summary:**
Updated all 62 command files in `.claude/commands` directory to improve parameter documentation clarity by replacing `examples` field with descriptive `argument-hint` field.

**Changes:**
- Added/improved `argument-hint` for all commands based on usage patterns
- Removed `examples` field and all example items from YAML headers
- Maintained all other YAML fields (name, description, usage, allowed-tools)
- Deleted obsolete commands: workflow/issue/*, workflow/session/pause.md, workflow/session/switch.md
- Cleaned up temporary analysis files

**Rationale:**
The `argument-hint` field provides clearer, more concise parameter documentation than example lists, improving command discoverability and usability in the Claude Code interface.

**Files Modified:** 62 command files
**Lines Changed:** -1570 insertions, +192 deletions

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

2025-10-11 23:45:55 +08:00

3.8 KiB

Raw Blame History

name, description, usage, argument-hint, allowed-tools

name	description	usage	argument-hint	allowed-tools
analyze	Quick codebase analysis using CLI tools (codex/gemini/qwen)	/cli:analyze [--tool <codex\|gemini\|qwen>] [--enhance] <analysis-target>	[--tool codex\|gemini\|qwen] [--enhance] analysis target	SlashCommand(), Bash(), TodoWrite(), Read(), Glob(*)

CLI Analyze Command (/cli:analyze)

Purpose

Quick codebase analysis using CLI tools. Analysis only - does NOT modify code.

Intent: Understand code patterns, architecture, and provide insights/recommendations Supported Tools: codex, gemini (default), qwen

Core Behavior

Read-Only Analysis: This command ONLY analyzes code and provides insights
No Code Modification: Results are recommendations and analysis reports
Template-Based: Automatically selects appropriate analysis template
Smart Pattern Detection: Infers relevant files based on analysis target

Parameters

--tool <codex|gemini|qwen> - Tool selection (default: gemini)
--enhance - Use /enhance-prompt for context-aware enhancement
<analysis-target> - Description of what to analyze

Execution Flow

Parse tool selection (default: gemini)
If --enhance: Execute /enhance-prompt first to expand user intent
Auto-detect analysis type from keywords → select template
Build command with auto-detected file patterns and MODE: analysis
Execute analysis (read-only, no code changes)
Return analysis report with insights and recommendations

File Pattern Auto-Detection

Keywords trigger specific file patterns:

"auth" → @{**/*auth*,**/*user*}
"component" → @{src/components/**/*,**/*.component.*}
"API" → @{**/api/**/*,**/routes/**/*}
"test" → @{**/*.test.*,**/*.spec.*}
"config" → @{*.config.*,**/config/**/*}
Generic → @{src/**/*}

For complex patterns, use rg or MCP tools to discover files first, then execute CLI with precise file references.

Command Template

cd . && ~/.claude/scripts/gemini-wrapper -p "
PURPOSE: [analysis goal from target]
TASK: [auto-detected analysis type]
MODE: analysis
CONTEXT: @{CLAUDE.md} [auto-detected file patterns]
EXPECTED: Insights, patterns, recommendations (NO code modification)
RULES: [auto-selected template] | Focus on [analysis aspect]
"

Examples

Basic Analysis:

/cli:analyze "authentication patterns"
# Executes: Gemini analysis with auth file patterns
# Returns: Pattern analysis, architecture insights, recommendations

Architecture Analysis:

/cli:analyze --tool qwen "component architecture"
# Executes: Qwen with component file patterns
# Returns: Architecture review, design patterns, improvement suggestions

Performance Analysis:

/cli:analyze --tool codex "performance bottlenecks"
# Executes: Codex deep analysis with performance focus
# Returns: Bottleneck identification, optimization recommendations

Enhanced Analysis:

/cli:analyze --enhance "fix auth issues"
# Step 1: Enhance prompt to expand context
# Step 2: Analysis with expanded context
# Returns: Root cause analysis, fix recommendations (NO automatic fixes)

Output Routing

Output Destination Logic:

Active session exists AND analysis is session-relevant:
- Save to .workflow/WFS-[id]/.chat/analyze-[timestamp].md
No active session OR one-off analysis:
- Save to .workflow/.scratchpad/analyze-[description]-[timestamp].md

Examples:

During active session WFS-auth-system, analyzing auth patterns → .chat/analyze-20250105-143022.md
No session, quick security check → .scratchpad/analyze-security-20250105-143045.md

Notes

Command templates, file patterns, and best practices: see intelligent-tools-strategy.md (loaded in memory)
Scratchpad directory details: see workflow-architecture.md
Scratchpad files can be promoted to workflow sessions if analysis proves valuable

3.8 KiB Raw Blame History