mirror of
https://github.com/catlog22/Claude-Code-Workflow.git
synced 2026-02-10 02:24:35 +08:00
- Consolidate Gemini, Qwen, and Codex commands into unified CLI commands - Add new code-analysis mode template - Update context-gather documentation - Remove redundant tool-specific command files 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
5.3 KiB
5.3 KiB
name, description, usage, argument-hint, examples, allowed-tools, model
| name | description | usage | argument-hint | examples | allowed-tools | model | |||
|---|---|---|---|---|---|---|---|---|---|
| chat | Simple CLI interaction command for direct codebase analysis | /cli:chat [--tool <codex|gemini|qwen>] [--enhance] "inquiry" | [--tool codex|gemini|qwen] [--enhance] inquiry |
|
SlashCommand(*), Bash(*) | sonnet |
🚀 Command Overview: /cli:chat
- Type: CLI Tool Wrapper for Interactive Analysis
- Purpose: Direct interaction with CLI tools for codebase analysis
- Supported Tools: codex, gemini (default), qwen
📥 Parameters & Usage
<inquiry>(Required): Your question or analysis request--tool <codex|gemini|qwen>(Optional): Select CLI tool (default: gemini)--enhance(Optional): Enhance inquiry with/enhance-promptbefore execution--all-files(Optional): Includes the entire codebase in the analysis context--save-session(Optional): Saves the interaction to current workflow session directory- File References: Specify files or patterns using
@{path/to/file}syntax
🔄 Execution Workflow
Parse Tool -> Parse Input -> [Optional] Enhance -> Assemble Context -> Construct Prompt -> Execute CLI Tool -> (Optional) Save Session
🛠️ Tool Selection
| Tool | Best For | Wrapper |
|---|---|---|
| gemini (default) | General analysis, exploration | ~/.claude/scripts/gemini-wrapper |
| qwen | Architecture, design patterns | ~/.claude/scripts/qwen-wrapper |
| codex | Development queries, deep analysis | codex --full-auto exec |
🔄 Original Execution Workflow
Parse Input -> [Optional] Enhance -> Assemble Context -> Construct Prompt -> Execute Gemini CLI -> (Optional) Save Session
🎯 Enhancement Integration
When --enhance flag present:
# Step 1: Enhance the inquiry
SlashCommand(command="/enhance-prompt \"[inquiry]\"")
# Step 2: Use enhanced output for chat
# Enhanced output provides enriched context and structured intent
Example:
# User: /gemini:chat --enhance "fix the login"
# Step 1: Enhance
/enhance-prompt "fix the login"
# Returns:
# INTENT: Debug login authentication failure
# CONTEXT: JWT auth in src/auth/, session state issue
# ACTION: Check token validation → verify middleware → test flow
# Step 2: Chat with enhanced context
gemini -p "Debug login authentication failure. Focus on JWT token validation
in src/auth/, verify middleware integration, and test authentication flow.
Known issue: session state management"
📚 Context Assembly
Context is gathered from:
- Project Guidelines: Always includes
@{CLAUDE.md,**/*CLAUDE.md} - User-Explicit Files: Files specified by the user (e.g.,
@{src/auth/*.js}) - All Files Flag: The
--all-filesflag includes the entire codebase
📝 Prompt Format
Core Guidelines: @~/.claude/workflows/intelligent-tools-strategy.md
cd [directory] && ~/.claude/scripts/gemini-wrapper -p "
PURPOSE: [clear analysis/inquiry goal]
TASK: [specific analysis or question]
CONTEXT: @{CLAUDE.md,**/*CLAUDE.md} @{target_files}
EXPECTED: [expected response format]
RULES: [constraints or focus areas]
"
⚙️ Execution Implementation
Standard Template:
cd . && ~/.claude/scripts/gemini-wrapper -p "
PURPOSE: [user inquiry goal]
TASK: [specific question or analysis]
CONTEXT: @{CLAUDE.md,**/*CLAUDE.md} @{inferred_or_specified_files}
EXPECTED: Analysis with file references and code examples
RULES: [focus areas based on inquiry]
"
With --all-files flag:
cd . && ~/.claude/scripts/gemini-wrapper --all-files -p "
PURPOSE: [user inquiry goal]
TASK: [specific question or analysis]
CONTEXT: @{CLAUDE.md,**/*CLAUDE.md} [entire codebase]
EXPECTED: Comprehensive analysis across all files
RULES: [focus areas based on inquiry]
"
Example - Authentication Analysis:
cd . && ~/.claude/scripts/gemini-wrapper -p "
PURPOSE: Understand authentication flow implementation
TASK: Analyze authentication flow and identify patterns
CONTEXT: @{**/*auth*,**/*login*} @{CLAUDE.md}
EXPECTED: Flow diagram, security assessment, integration points
RULES: Focus on security patterns and JWT handling
"
Example - Performance Optimization:
cd src/components && ~/.claude/scripts/gemini-wrapper -p "
PURPOSE: Optimize React component performance
TASK: Identify performance bottlenecks in component rendering
CONTEXT: @{**/*.{jsx,tsx}} @{CLAUDE.md}
EXPECTED: Specific optimization recommendations with file:line references
RULES: Focus on re-render patterns and memoization opportunities
"
💾 Session Persistence
When --save-session flag is used:
- Check for existing active session (
.workflow/.active-*markers) - Save to existing session's
.chat/directory or create new session - File format:
chat-YYYYMMDD-HHMMSS.md - Include query, context, and response in saved file
Session Template:
# Chat Session: [Timestamp]
## Query
[Original user inquiry]
## Context
[Files and patterns included in analysis]
## Gemini Response
[Complete response from Gemini CLI]