mirror of
https://github.com/catlog22/Claude-Code-Workflow.git
synced 2026-02-11 02:33:51 +08:00
ff1ca34c2e
Major Changes: - Merge tools-implementation-guide.md into intelligent-tools-strategy.md - Consolidate TEMPLATE and RULES fields into single RULES field - Standardize template references using $(cat ...) format - Reduce document length by 66% (520→177 lines) while preserving core functionality Template System Improvements: - Universal 4-field command format: PURPOSE | TASK | EXPECTED | RULES - Unified rules format: $(cat template.txt) | constraints - Comprehensive template directory structure with examples - Cross-tool template compatibility and reuse patterns Content Optimization: - Remove redundant examples and duplicate content - Focus on universal command templates and common scenarios - Simplify tool selection matrix with clear task-to-tool mapping - Streamline workflow integration with essential best practices 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
3.1 KiB
3.1 KiB
name, description, usage, argument-hint, examples, model
| name | description | usage | argument-hint | examples | model | ||||
|---|---|---|---|---|---|---|---|---|---|
| analyze | Quick analysis of codebase patterns, architecture, and code quality using Gemini CLI | /gemini:analyze <analysis-type> | analysis target or type |
|
haiku |
Gemini Analysis Command (/gemini:analyze)
Overview
Quick analysis tool for codebase insights using intelligent pattern detection and template-driven analysis.
Core Guidelines: @~/.claude/workflows/intelligent-tools-strategy.md
Analysis Types
| Type | Purpose | Example |
|---|---|---|
| pattern | Code pattern detection | "React hooks usage patterns" |
| architecture | System structure analysis | "component hierarchy structure" |
| security | Security vulnerabilities | "authentication vulnerabilities" |
| performance | Performance bottlenecks | "rendering performance issues" |
| quality | Code quality assessment | "testing coverage analysis" |
| dependencies | Third-party analysis | "outdated package dependencies" |
Quick Usage
Basic Analysis
/gemini:analyze "authentication patterns"
Executes: gemini -p -a "@{**/*auth*} @{CLAUDE.md} $(template:analysis/pattern.txt)"
Targeted Analysis
/gemini:analyze "React component architecture"
Executes: gemini -p -a "@{src/components/**/*} @{CLAUDE.md} $(template:analysis/architecture.txt)"
Security Focus
/gemini:analyze "API security vulnerabilities"
Executes: gemini -p -a "@{**/api/**/*} @{CLAUDE.md} $(template:analysis/security.txt)"
Templates Used
Templates are automatically selected based on analysis type:
- Pattern Analysis:
~/.claude/workflows/cli-templates/prompts/analysis/pattern.txt - Architecture Analysis:
~/.claude/workflows/cli-templates/prompts/analysis/architecture.txt - Security Analysis:
~/.claude/workflows/cli-templates/prompts/analysis/security.txt - Performance Analysis:
~/.claude/workflows/cli-templates/prompts/analysis/performance.txt
Workflow Integration
⚠️ Session Check: Automatically detects active workflow session via .workflow/.active-* marker file.
Analysis results saved to:
- Active session:
.workflow/WFS-[topic]/.chat/analysis-[timestamp].md - No session: Temporary analysis output
Common Patterns
Technology Stack Analysis
/gemini:analyze "project technology stack"
# Auto-detects: package.json, config files, dependencies
Code Quality Review
/gemini:analyze "code quality and standards"
# Auto-targets: source files, test files, CLAUDE.md
Migration Planning
/gemini:analyze "legacy code modernization"
# Focuses: older patterns, deprecated APIs, upgrade paths
Output Format
Analysis results include:
- File References: Specific file:line locations
- Code Examples: Relevant code snippets
- Patterns Found: Common patterns and anti-patterns
- Recommendations: Actionable improvements
- Integration Points: How components connect