mirror of
https://github.com/catlog22/Claude-Code-Workflow.git
synced 2026-02-12 02:37:45 +08:00
Updates all command files to use consistent naming without parent field: - Remove parent field from all command frontmatter - Standardize name field to use simple names instead of prefixed names - Fix usage patterns for brainstorm commands to use proper workflow namespace - Add new medium-project-update.sh script for batch updates 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
3.6 KiB
3.6 KiB
name, description, usage, argument-hint, examples, allowed-tools, model
| name | description | usage | argument-hint | examples | allowed-tools | model | |||
|---|---|---|---|---|---|---|---|---|---|
| bug-fix | Bug analysis and fix suggestions using specialized template | /gemini:chat:bug-fix "bug description" | description of the bug or error you're experiencing |
|
Bash(gemini:*) | sonnet |
🐛 Command Overview: /gemini:chat:bug-fix
- 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:
- Bug-Fix Template: @~/.claude/prompt-templates/bug-fix.md
- Project Guidelines: @{CLAUDE.md,**/*CLAUDE.md}
- Relevant Files: User-specified files or all files if
--all-filesused
📝 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
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-fix-YYYYMMDD-HHMMSS.md - Includes template used, bug description, analysis, and recommendations
Session Template:
# 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]