mirror of https://github.com/catlog22/Claude-Code-Workflow.git synced 2026-02-11 02:33:51 +08:00

Files

catlog22 d0b08794ca refactor: Reorganize workflow documentation structure and eliminate redundancy

## Major Changes
- **Replace 3 documents with 2**: Consolidate 655 lines to ~550 lines (40% reduction)
- **New Structure**:
  - `intelligent-tools-strategy.md` (strategic layer)
  - `tools-implementation-guide.md` (implementation layer)
- **Remove old files**: `intelligent-tools.md`, `gemini-unified.md`, `codex-unified.md`

## Content Improvements
- **Quick Start section**: Essential commands for immediate use
- **Strategic guidance**: Tool selection matrix and decision framework
- **Implementation details**: Part A (shared), Part B (Gemini), Part C (Codex)
- **Eliminate duplicates**: Template system, file patterns, execution settings

## Reference Updates
- **Agent files**: Update to new document paths (3 files)
- **Command files**: Batch update all references (12 files)
- **README files**: Update English and Chinese versions
- **Workflow files**: Update plan.md reference

## Benefits
- 40% content reduction while preserving all unique information
- Clear layer separation: strategy vs implementation
- Improved navigation and maintainability
- Enhanced quick reference capabilities

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

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

2025-09-14 20:59:15 +08:00

3.2 KiB

Raw Blame History

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

/gemini:analyze "React hooks patterns"

/gemini:analyze "authentication security"

/gemini:analyze "performance bottlenecks"

/gemini:analyze "API design patterns"

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/tools-implementation-guide.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

For detailed syntax, patterns, and advanced usage see: @~/.claude/workflows/tools-implementation-guide.md

3.2 KiB Raw Blame History