mirror of
https://github.com/catlog22/Claude-Code-Workflow.git
synced 2026-02-13 02:41:50 +08:00
refactor: Reorganize Gemini commands - move bug-fix to pre/bug-index
- Move bug-fix.md from gemini/chat/ to gemini/pre/bug-index.md - Update command name from bug-fix to bug-index - Update all command references to use /gemini:pre:bug-index path - Delete obsolete chat/plan.md file - Maintain template functionality while improving command organization 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
catlog22
113
.claude/commands/gemini/pre/bug-index.md
Normal file
113
.claude/commands/gemini/pre/bug-index.md
Normal file
@@ -0,0 +1,113 @@
|
||||
---
|
||||
name: bug-index
|
||||
|
||||
description: Bug analysis and fix suggestions using specialized template
|
||||
usage: /gemini:pre:bug-index "bug description"
|
||||
argument-hint: "description of the bug or error you're experiencing"
|
||||
examples:
|
||||
- /gemini:pre:bug-index "authentication null pointer error in login flow"
|
||||
- /gemini:pre:bug-index "React component not re-rendering after state change"
|
||||
- /gemini:pre:bug-index "database connection timeout in production"
|
||||
allowed-tools: Bash(gemini:*)
|
||||
model: sonnet
|
||||
---
|
||||
|
||||
### 🐛 **Command Overview: `/gemini:pre:bug-index`**
|
||||
|
||||
- **Type**: Template-based Gemini CLI Wrapper
|
||||
- **Purpose**: Specialized bug analysis and fix suggestions using expert diagnostic template
|
||||
- **Template**: Bug fix analysis template for systematic problem diagnosis
|
||||
- **Core Tool**: `Bash(gemini:*)` - Executes Gemini CLI with bug-fix template
|
||||
|
||||
### 📥 **Parameters & Usage**
|
||||
|
||||
- **`<bug description>` (Required)**: Description of the bug, error, or unexpected behavior
|
||||
- **`--all-files` (Optional)**: Includes entire codebase for comprehensive analysis
|
||||
- **`--save-session` (Optional)**: Saves the bug analysis to current workflow session
|
||||
|
||||
### 🔄 **Execution Workflow**
|
||||
|
||||
`Parse Bug Description` **->** `Load Bug-Fix Template` **->** `Assemble Context` **->** `Execute Gemini CLI` **->** `(Optional) Save Session`
|
||||
|
||||
### 📋 **Bug Analysis Focus**
|
||||
|
||||
The bug-fix template provides structured analysis covering:
|
||||
- **Root Cause Analysis**: Systematic investigation of underlying issues
|
||||
- **Code Path Tracing**: Following execution flow to identify failure points
|
||||
- **Hypothesis Validation**: Testing theories about bug origins
|
||||
- **Targeted Solutions**: Specific, minimal fixes rather than broad refactoring
|
||||
- **Impact Assessment**: Understanding side effects of proposed fixes
|
||||
|
||||
### 📚 **Context Assembly**
|
||||
|
||||
Context includes:
|
||||
1. **Bug-Fix Template**: @~/.claude/prompt-templates/bug-fix.md
|
||||
2. **Project Guidelines**: @{CLAUDE.md,**/*CLAUDE.md}
|
||||
3. **Relevant Files**: User-specified files or all files if `--all-files` used
|
||||
|
||||
### 📝 **Prompt Structure**
|
||||
|
||||
```
|
||||
=== SYSTEM PROMPT ===
|
||||
@~/.claude/prompt-templates/bug-fix.md
|
||||
|
||||
=== CONTEXT ===
|
||||
@{CLAUDE.md,**/*CLAUDE.md}
|
||||
@{target_files}
|
||||
|
||||
=== USER INPUT ===
|
||||
[Bug description and any relevant details]
|
||||
```
|
||||
|
||||
### ⚙️ **Implementation**
|
||||
|
||||
```pseudo
|
||||
FUNCTION execute_bug_fix_analysis(bug_description, flags):
|
||||
// Load bug-fix template
|
||||
template = load_file(@~/.claude/prompt-templates/bug-fix.md)
|
||||
|
||||
// Construct prompt with template
|
||||
prompt = "=== SYSTEM PROMPT ===\n" + template + "\n\n"
|
||||
prompt += "=== CONTEXT ===\n"
|
||||
prompt += "@{CLAUDE.md,**/*CLAUDE.md}\n"
|
||||
|
||||
// Execute with appropriate context
|
||||
IF flags contain "--all-files":
|
||||
result = execute_tool("Bash(gemini:*)", "--all-files", "-p", prompt + bug_description)
|
||||
ELSE:
|
||||
prompt += "\n=== USER INPUT ===\n" + bug_description
|
||||
result = execute_tool("Bash(gemini:*)", "-p", prompt)
|
||||
|
||||
// Save session if requested
|
||||
IF flags contain "--save-session":
|
||||
save_bug_analysis_session(bug_description, result)
|
||||
|
||||
RETURN result
|
||||
END FUNCTION
|
||||
```
|
||||
|
||||
### 💾 **Session Integration**
|
||||
|
||||
When `--save-session` is used:
|
||||
- Saves to `.workflow/WFS-[topic]/.chat/` directory
|
||||
- File named: `bug-index-YYYYMMDD-HHMMSS.md`
|
||||
- Includes template used, bug description, analysis, and recommendations
|
||||
|
||||
**Session Template:**
|
||||
```markdown
|
||||
# Bug Fix Analysis: [Timestamp]
|
||||
|
||||
## Bug Description
|
||||
[Original bug description]
|
||||
|
||||
## Template Used
|
||||
bug-fix.md - Expert diagnostic analysis template
|
||||
|
||||
## Analysis Results
|
||||
[Complete Gemini response with root cause analysis and fix suggestions]
|
||||
|
||||
## Recommended Actions
|
||||
- [Immediate fixes]
|
||||
- [Prevention measures]
|
||||
- [Testing recommendations]
|
||||
```
|
||||
117
.claude/commands/gemini/pre/plan.md
Normal file
117
.claude/commands/gemini/pre/plan.md
Normal file
@@ -0,0 +1,117 @@
|
||||
---
|
||||
name: plan
|
||||
description: Project planning and architecture analysis using specialized template
|
||||
usage: /gemini:chat:plan "planning topic"
|
||||
argument-hint: "planning topic or architectural challenge to analyze"
|
||||
examples:
|
||||
- /gemini:chat:plan "design user dashboard feature architecture"
|
||||
- /gemini:chat:plan "plan microservices migration strategy"
|
||||
- /gemini:chat:plan "implement real-time notification system"
|
||||
allowed-tools: Bash(gemini:*)
|
||||
model: sonnet
|
||||
---
|
||||
|
||||
### 📋 **Command Overview: `/gemini:chat:plan`**
|
||||
|
||||
- **Type**: Template-based Gemini CLI Wrapper
|
||||
- **Purpose**: Comprehensive project planning and architecture analysis using expert planning template
|
||||
- **Template**: Planning analysis template for systematic feature and system design
|
||||
- **Core Tool**: `Bash(gemini:*)` - Executes Gemini CLI with planning template
|
||||
|
||||
### 📥 **Parameters & Usage**
|
||||
|
||||
- **`<planning topic>` (Required)**: Description of the feature, system, or architectural challenge to plan
|
||||
- **`--all-files` (Optional)**: Includes entire codebase for comprehensive planning context
|
||||
- **`--save-session` (Optional)**: Saves the planning analysis to current workflow session
|
||||
|
||||
### 🔄 **Execution Workflow**
|
||||
|
||||
`Parse Planning Topic` **->** `Load Planning Template` **->** `Assemble Context` **->** `Execute Gemini CLI` **->** `(Optional) Save Session`
|
||||
|
||||
### 📋 **Planning Analysis Focus**
|
||||
|
||||
The planning template provides structured analysis covering:
|
||||
- **Requirements Analysis**: Understanding functional and non-functional requirements
|
||||
- **Architecture Design**: System structure, components, and interactions
|
||||
- **Implementation Strategy**: Step-by-step development approach
|
||||
- **Risk Assessment**: Identifying potential challenges and mitigation strategies
|
||||
- **Resource Planning**: Time, effort, and technology requirements
|
||||
|
||||
### 📚 **Context Assembly**
|
||||
|
||||
Context includes:
|
||||
1. **Planning Template**: @~/.claude/prompt-templates/plan.md
|
||||
2. **Project Guidelines**: @{CLAUDE.md,**/*CLAUDE.md}
|
||||
3. **Relevant Files**: User-specified files or all files if `--all-files` used
|
||||
|
||||
### 📝 **Prompt Structure**
|
||||
|
||||
```
|
||||
=== SYSTEM PROMPT ===
|
||||
@~/.claude/prompt-templates/plan.md
|
||||
|
||||
=== CONTEXT ===
|
||||
@{CLAUDE.md,**/*CLAUDE.md}
|
||||
@{target_files}
|
||||
|
||||
=== USER INPUT ===
|
||||
[Planning topic and any specific requirements or constraints]
|
||||
```
|
||||
|
||||
### ⚙️ **Implementation**
|
||||
|
||||
```pseudo
|
||||
FUNCTION execute_planning_analysis(planning_topic, flags):
|
||||
// Load planning template
|
||||
template = load_file(@~/.claude/prompt-templates/plan.md)
|
||||
|
||||
// Construct prompt with template
|
||||
prompt = "=== SYSTEM PROMPT ===\n" + template + "\n\n"
|
||||
prompt += "=== CONTEXT ===\n"
|
||||
prompt += "@{CLAUDE.md,**/*CLAUDE.md}\n"
|
||||
|
||||
// Execute with appropriate context
|
||||
IF flags contain "--all-files":
|
||||
result = execute_tool("Bash(gemini:*)", "--all-files", "-p", prompt + planning_topic)
|
||||
ELSE:
|
||||
prompt += "\n=== USER INPUT ===\n" + planning_topic
|
||||
result = execute_tool("Bash(gemini:*)", "-p", prompt)
|
||||
|
||||
// Save session if requested
|
||||
IF flags contain "--save-session":
|
||||
save_planning_session(planning_topic, result)
|
||||
|
||||
RETURN result
|
||||
END FUNCTION
|
||||
```
|
||||
|
||||
### 💾 **Session Integration**
|
||||
|
||||
When `--save-session` is used:
|
||||
- Saves to `.workflow/WFS-[topic]/.chat/` directory
|
||||
- File named: `plan-YYYYMMDD-HHMMSS.md`
|
||||
- Includes template used, planning topic, analysis, and implementation roadmap
|
||||
|
||||
**Session Template:**
|
||||
```markdown
|
||||
# Planning Analysis: [Timestamp]
|
||||
|
||||
## Planning Topic
|
||||
[Original planning topic description]
|
||||
|
||||
## Template Used
|
||||
plan.md - Expert planning and architecture analysis template
|
||||
|
||||
## Analysis Results
|
||||
[Complete Gemini response with requirements, architecture, and implementation plan]
|
||||
|
||||
## Implementation Roadmap
|
||||
- [Phase 1: Foundation work]
|
||||
- [Phase 2: Core implementation]
|
||||
- [Phase 3: Integration and testing]
|
||||
|
||||
## Key Decisions
|
||||
- [Architecture choices]
|
||||
- [Technology selections]
|
||||
- [Risk mitigation strategies]
|
||||
```
|
||||
Reference in New Issue
Block a user