mirror of
https://github.com/catlog22/Claude-Code-Workflow.git
synced 2026-02-05 01:50:27 +08:00
refactor: Standardize command naming conventions and remove parent relationships
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>
This commit is contained in:
catlog22
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: gemini-analyze
|
||||
parent: /gemini
|
||||
name: analyze
|
||||
|
||||
description: Advanced Gemini CLI analysis with template-driven pattern detection and comprehensive codebase insights
|
||||
usage: /gemini:analyze <target>
|
||||
argument-hint: "analysis target or description"
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: gemini-chat
|
||||
parent: /gemini
|
||||
name: chat
|
||||
|
||||
description: Simple Gemini CLI interaction command for direct codebase analysis
|
||||
usage: /gemini:chat "inquiry"
|
||||
argument-hint: "your question or analysis request"
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: bug-fix
|
||||
parent: /gemini/chat
|
||||
|
||||
description: Bug analysis and fix suggestions using specialized template
|
||||
usage: /gemini:chat:bug-fix "bug description"
|
||||
argument-hint: "description of the bug or error you're experiencing"
|
||||
|
||||
@@ -1,6 +1,5 @@
|
||||
---
|
||||
name: plan
|
||||
parent: /gemini/chat
|
||||
description: Project planning and architecture analysis using specialized template
|
||||
usage: /gemini:chat:plan "planning topic"
|
||||
argument-hint: "planning topic or architectural challenge to analyze"
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: gemini-execute
|
||||
parent: /gemini
|
||||
name: execute
|
||||
|
||||
description: Intelligent context inference executor with auto-approval capabilities, supporting user descriptions and task ID execution modes
|
||||
usage: /gemini:execute <description|task-id>
|
||||
argument-hint: "implementation description or task-id"
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
name: task-breakdown
|
||||
name: breakdown
|
||||
description: Intelligent task decomposition with context-aware subtask generation
|
||||
usage: /task:breakdown <task-id>
|
||||
argument-hint: task-id
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
name: task-create
|
||||
name: create
|
||||
description: Create implementation tasks with automatic context awareness
|
||||
usage: /task:create "title"
|
||||
argument-hint: "task title"
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
name: task-execute
|
||||
name: execute
|
||||
description: Execute tasks with appropriate agents and context-aware orchestration
|
||||
usage: /task:execute <task-id>
|
||||
argument-hint: task-id
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
name: task-replan
|
||||
name: replan
|
||||
description: Replan individual tasks with detailed user input and change tracking
|
||||
usage: /task:replan <task-id> [input]
|
||||
argument-hint: task-id ["text"|file.md|ISS-001]
|
||||
|
||||
@@ -1,12 +1,12 @@
|
||||
---
|
||||
name: brainstorm:business-analyst
|
||||
name: business-analyst
|
||||
description: Business analyst perspective brainstorming for process optimization and business efficiency analysis
|
||||
usage: /brainstorm:business-analyst <topic>
|
||||
usage: /workflow:brainstorm:business-analyst <topic>
|
||||
argument-hint: "topic or challenge to analyze from business analysis perspective"
|
||||
examples:
|
||||
- /brainstorm:business-analyst "workflow automation opportunities"
|
||||
- /brainstorm:business-analyst "business process optimization"
|
||||
- /brainstorm:business-analyst "cost reduction initiatives"
|
||||
- /workflow:brainstorm:business-analyst "workflow automation opportunities"
|
||||
- /workflow:brainstorm:business-analyst "business process optimization"
|
||||
- /workflow:brainstorm:business-analyst "cost reduction initiatives"
|
||||
allowed-tools: Task(conceptual-planning-agent), TodoWrite(*)
|
||||
---
|
||||
|
||||
|
||||
@@ -1,12 +1,12 @@
|
||||
---
|
||||
name: brainstorm:data-architect
|
||||
name: data-architect
|
||||
description: Data architect perspective brainstorming for data modeling, flow, and analytics analysis
|
||||
usage: /brainstorm:data-architect <topic>
|
||||
usage: /workflow:brainstorm:data-architect <topic>
|
||||
argument-hint: "topic or challenge to analyze from data architecture perspective"
|
||||
examples:
|
||||
- /brainstorm:data-architect "user analytics data pipeline"
|
||||
- /brainstorm:data-architect "real-time data processing system"
|
||||
- /brainstorm:data-architect "data warehouse modernization"
|
||||
- /workflow:brainstorm:data-architect "user analytics data pipeline"
|
||||
- /workflow:brainstorm:data-architect "real-time data processing system"
|
||||
- /workflow:brainstorm:data-architect "data warehouse modernization"
|
||||
allowed-tools: Task(conceptual-planning-agent), TodoWrite(*)
|
||||
---
|
||||
|
||||
|
||||
@@ -1,12 +1,12 @@
|
||||
---
|
||||
name: brainstorm:feature-planner
|
||||
name: planner
|
||||
description: Feature planner perspective brainstorming for feature development and planning analysis
|
||||
usage: /brainstorm:feature-planner <topic>
|
||||
usage: /workflow:brainstorm:feature-planner <topic>
|
||||
argument-hint: "topic or challenge to analyze from feature planning perspective"
|
||||
examples:
|
||||
- /brainstorm:feature-planner "user dashboard enhancement"
|
||||
- /brainstorm:feature-planner "mobile app feature roadmap"
|
||||
- /brainstorm:feature-planner "integration capabilities planning"
|
||||
- /workflow:brainstorm:feature-planner "user dashboard enhancement"
|
||||
- /workflow:brainstorm:feature-planner "mobile app feature roadmap"
|
||||
- /workflow:brainstorm:feature-planner "integration capabilities planning"
|
||||
allowed-tools: Task(conceptual-planning-agent), TodoWrite(*)
|
||||
---
|
||||
|
||||
|
||||
@@ -1,12 +1,12 @@
|
||||
---
|
||||
name: brainstorm:innovation-lead
|
||||
name: innovation-lead
|
||||
description: Innovation lead perspective brainstorming for emerging technologies and future opportunities analysis
|
||||
usage: /brainstorm:innovation-lead <topic>
|
||||
usage: /workflow:brainstorm:innovation-lead <topic>
|
||||
argument-hint: "topic or challenge to analyze from innovation and emerging technology perspective"
|
||||
examples:
|
||||
- /brainstorm:innovation-lead "AI integration opportunities"
|
||||
- /brainstorm:innovation-lead "future technology trends"
|
||||
- /brainstorm:innovation-lead "disruptive innovation strategy"
|
||||
- /workflow:brainstorm:innovation-lead "AI integration opportunities"
|
||||
- /workflow:brainstorm:innovation-lead "future technology trends"
|
||||
- /workflow:brainstorm:innovation-lead "disruptive innovation strategy"
|
||||
allowed-tools: Task(conceptual-planning-agent), TodoWrite(*)
|
||||
---
|
||||
|
||||
|
||||
@@ -1,12 +1,12 @@
|
||||
---
|
||||
name: brainstorm:product-manager
|
||||
name: product-manager
|
||||
description: Product manager perspective brainstorming for user needs and business value analysis
|
||||
usage: /brainstorm:product-manager <topic>
|
||||
usage: /workflow:brainstorm:product-manager <topic>
|
||||
argument-hint: "topic or challenge to analyze from product management perspective"
|
||||
examples:
|
||||
- /brainstorm:product-manager "user authentication redesign"
|
||||
- /brainstorm:product-manager "mobile app performance optimization"
|
||||
- /brainstorm:product-manager "feature prioritization strategy"
|
||||
- /workflow:brainstorm:product-manager "user authentication redesign"
|
||||
- /workflow:brainstorm:product-manager "mobile app performance optimization"
|
||||
- /workflow:brainstorm:product-manager "feature prioritization strategy"
|
||||
allowed-tools: Task(conceptual-planning-agent), TodoWrite(*)
|
||||
---
|
||||
|
||||
|
||||
@@ -1,12 +1,12 @@
|
||||
---
|
||||
name: brainstorm:security-expert
|
||||
name: security-expert
|
||||
description: Security expert perspective brainstorming for threat modeling and security architecture analysis
|
||||
usage: /brainstorm:security-expert <topic>
|
||||
usage: /workflow:brainstorm:security-expert <topic>
|
||||
argument-hint: "topic or challenge to analyze from cybersecurity perspective"
|
||||
examples:
|
||||
- /brainstorm:security-expert "user authentication security review"
|
||||
- /brainstorm:security-expert "API security architecture"
|
||||
- /brainstorm:security-expert "data protection compliance strategy"
|
||||
- /workflow:brainstorm:security-expert "user authentication security review"
|
||||
- /workflow:brainstorm:security-expert "API security architecture"
|
||||
- /workflow:brainstorm:security-expert "data protection compliance strategy"
|
||||
allowed-tools: Task(conceptual-planning-agent), TodoWrite(*)
|
||||
---
|
||||
|
||||
|
||||
@@ -1,10 +1,10 @@
|
||||
---
|
||||
name: brainstorm:synthesis
|
||||
name: synthesis
|
||||
description: Synthesize all brainstorming role perspectives into comprehensive analysis and recommendations
|
||||
usage: /brainstorm:synthesis
|
||||
usage: /workflow:brainstorm:synthesis
|
||||
argument-hint: "no arguments required - analyzes existing brainstorming session outputs"
|
||||
examples:
|
||||
- /brainstorm:synthesis
|
||||
- /workflow:brainstorm:synthesis
|
||||
allowed-tools: Read(*), Write(*), TodoWrite(*), Glob(*)
|
||||
---
|
||||
|
||||
|
||||
@@ -1,12 +1,12 @@
|
||||
---
|
||||
name: brainstorm:system-architect
|
||||
name: system-architect
|
||||
description: System architect perspective brainstorming for technical architecture and scalability analysis
|
||||
usage: /brainstorm:system-architect <topic>
|
||||
usage: /workflow:brainstorm:system-architect <topic>
|
||||
argument-hint: "topic or challenge to analyze from system architecture perspective"
|
||||
examples:
|
||||
- /brainstorm:system-architect "user authentication redesign"
|
||||
- /brainstorm:system-architect "microservices migration strategy"
|
||||
- /brainstorm:system-architect "system performance optimization"
|
||||
- /workflow:brainstorm:system-architect "user authentication redesign"
|
||||
- /workflow:brainstorm:system-architect "microservices migration strategy"
|
||||
- /workflow:brainstorm:system-architect "system performance optimization"
|
||||
allowed-tools: Task(conceptual-planning-agent), TodoWrite(*)
|
||||
---
|
||||
|
||||
|
||||
@@ -1,12 +1,12 @@
|
||||
---
|
||||
name: brainstorm:ui-designer
|
||||
name: ui-designer
|
||||
description: UI designer perspective brainstorming for user experience and interface design analysis
|
||||
usage: /brainstorm:ui-designer <topic>
|
||||
usage: /workflow:brainstorm:ui-designer <topic>
|
||||
argument-hint: "topic or challenge to analyze from UI/UX design perspective"
|
||||
examples:
|
||||
- /brainstorm:ui-designer "user authentication redesign"
|
||||
- /brainstorm:ui-designer "mobile app navigation improvement"
|
||||
- /brainstorm:ui-designer "accessibility enhancement strategy"
|
||||
- /workflow:brainstorm:ui-designer "user authentication redesign"
|
||||
- /workflow:brainstorm:ui-designer "mobile app navigation improvement"
|
||||
- /workflow:brainstorm:ui-designer "accessibility enhancement strategy"
|
||||
allowed-tools: Task(conceptual-planning-agent), TodoWrite(*)
|
||||
---
|
||||
|
||||
|
||||
@@ -1,12 +1,12 @@
|
||||
---
|
||||
name: brainstorm:user-researcher
|
||||
name: user-researcher
|
||||
description: User researcher perspective brainstorming for user behavior analysis and research insights
|
||||
usage: /brainstorm:user-researcher <topic>
|
||||
usage: /workflow:brainstorm:user-researcher <topic>
|
||||
argument-hint: "topic or challenge to analyze from user research perspective"
|
||||
examples:
|
||||
- /brainstorm:user-researcher "user onboarding experience"
|
||||
- /brainstorm:user-researcher "mobile app usability issues"
|
||||
- /brainstorm:user-researcher "feature adoption analysis"
|
||||
- /workflow:brainstorm:user-researcher "user onboarding experience"
|
||||
- /workflow:brainstorm:user-researcher "mobile app usability issues"
|
||||
- /workflow:brainstorm:user-researcher "feature adoption analysis"
|
||||
allowed-tools: Task(conceptual-planning-agent), TodoWrite(*)
|
||||
---
|
||||
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
name: workflow-execute
|
||||
name: execute
|
||||
description: Coordinate agents for existing workflow tasks with automatic discovery
|
||||
usage: /workflow:execute
|
||||
argument-hint: none
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
---
|
||||
name: workflow-issue-close
|
||||
name: close
|
||||
description: Close a completed or obsolete workflow issue
|
||||
usage: /workflow:issue:close <issue-id> [reason]
|
||||
parent: /workflow:issue
|
||||
|
||||
examples:
|
||||
- /workflow:issue:close ISS-001
|
||||
- /workflow:issue:close ISS-001 "Feature implemented in PR #42"
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
---
|
||||
name: workflow-issue-create
|
||||
name: create
|
||||
description: Create a new issue or change request
|
||||
usage: /workflow:issue:create "issue description"
|
||||
parent: /workflow:issue
|
||||
|
||||
examples:
|
||||
- /workflow:issue:create "Add OAuth2 social login support"
|
||||
- /workflow:issue:create "Fix user avatar security vulnerability"
|
||||
|
||||
@@ -1,8 +1,7 @@
|
||||
---
|
||||
name: workflow-issue-list
|
||||
name: list
|
||||
description: List and filter workflow issues
|
||||
usage: /workflow:issue:list
|
||||
parent: /workflow:issue
|
||||
examples:
|
||||
- /workflow:issue:list
|
||||
- /workflow:issue:list --open
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
---
|
||||
name: workflow-issue-update
|
||||
name: update
|
||||
description: Update an existing workflow issue
|
||||
usage: /workflow:issue:update <issue-id> [changes]
|
||||
parent: /workflow:issue
|
||||
|
||||
examples:
|
||||
- /workflow:issue:update ISS-001
|
||||
- /workflow:issue:update ISS-001 --priority=critical
|
||||
|
||||
@@ -1,15 +1,15 @@
|
||||
---
|
||||
name: workflow-plan-deep
|
||||
name: plan-deep
|
||||
description: Deep technical planning with Gemini CLI analysis and action-planning-agent
|
||||
usage: /workflow:plan:deep <task_description>
|
||||
usage: /workflow:plan-deep <task_description>
|
||||
argument-hint: "task description" | requirements.md
|
||||
examples:
|
||||
- /workflow:plan:deep "Refactor authentication system to use JWT"
|
||||
- /workflow:plan:deep "Implement real-time notifications across modules"
|
||||
- /workflow:plan:deep requirements.md
|
||||
- /workflow:plan-deep "Refactor authentication system to use JWT"
|
||||
- /workflow:plan-deep "Implement real-time notifications across modules"
|
||||
- /workflow:plan-deep requirements.md
|
||||
---
|
||||
|
||||
# Workflow Plan Deep Command (/workflow:plan:deep)
|
||||
# Workflow Plan Deep Command (/workflow:plan-deep)
|
||||
|
||||
## Overview
|
||||
Creates comprehensive implementation plans through deep codebase analysis using Gemini CLI and the action-planning-agent. This command enforces multi-dimensional context gathering before planning, ensuring technical decisions are grounded in actual codebase understanding.
|
||||
@@ -17,7 +17,7 @@ Creates comprehensive implementation plans through deep codebase analysis using
|
||||
## Key Differentiators
|
||||
|
||||
### vs /workflow:plan
|
||||
| Feature | /workflow:plan | /workflow:plan:deep |
|
||||
| Feature | /workflow:plan | /workflow:plan-deep |
|
||||
|---------|---------------|-------------------|
|
||||
| **Analysis Depth** | Basic requirements extraction | Deep codebase analysis |
|
||||
| **Gemini CLI** | Optional | **Mandatory (via agent)** |
|
||||
@@ -175,7 +175,7 @@ def process_plan_deep_command(input):
|
||||
|
||||
### Example 1: Cross-Module Refactoring
|
||||
```bash
|
||||
/workflow:plan:deep "Refactor user authentication to use JWT tokens across all services"
|
||||
/workflow:plan-deep "Refactor user authentication to use JWT tokens across all services"
|
||||
```
|
||||
Generates comprehensive plan analyzing:
|
||||
- Current auth implementation
|
||||
@@ -185,7 +185,7 @@ Generates comprehensive plan analyzing:
|
||||
|
||||
### Example 2: Performance Optimization
|
||||
```bash
|
||||
/workflow:plan:deep "Optimize database query performance in reporting module"
|
||||
/workflow:plan-deep "Optimize database query performance in reporting module"
|
||||
```
|
||||
Creates detailed plan including:
|
||||
- Current query patterns analysis
|
||||
@@ -195,7 +195,7 @@ Creates detailed plan including:
|
||||
|
||||
### Example 3: Architecture Enhancement
|
||||
```bash
|
||||
/workflow:plan:deep "Implement event-driven architecture for order processing"
|
||||
/workflow:plan-deep "Implement event-driven architecture for order processing"
|
||||
```
|
||||
Produces hierarchical plan with:
|
||||
- Current architecture assessment
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
name: workflow-plan
|
||||
name: plan
|
||||
description: Create implementation plans with intelligent input detection
|
||||
usage: /workflow:plan <input>
|
||||
argument-hint: "text description"|file.md|ISS-001|template-name
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
name: workflow-review
|
||||
name: review
|
||||
description: Execute review phase for quality validation
|
||||
usage: /workflow:review
|
||||
argument-hint: none
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
---
|
||||
name: workflow-session-list
|
||||
name: list
|
||||
description: List all workflow sessions with status
|
||||
usage: /workflow:session:list
|
||||
parent: /workflow:session
|
||||
|
||||
---
|
||||
|
||||
# List Workflow Sessions (/workflow/session/list)
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
---
|
||||
name: workflow-session-pause
|
||||
name: pause
|
||||
description: Pause the active workflow session
|
||||
usage: /workflow:session:pause
|
||||
parent: /workflow:session
|
||||
|
||||
---
|
||||
|
||||
# Pause Workflow Session (/workflow:session:pause)
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
---
|
||||
name: workflow-session-resume
|
||||
name: resume
|
||||
description: Resume the most recently paused workflow session
|
||||
usage: /workflow:session:resume
|
||||
parent: /workflow:session
|
||||
|
||||
---
|
||||
|
||||
# Resume Workflow Session (/workflow:session:resume)
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
---
|
||||
name: workflow-session-start
|
||||
name: start
|
||||
description: Start a new workflow session
|
||||
usage: /workflow:session:start "task description"
|
||||
parent: /workflow:session
|
||||
|
||||
examples:
|
||||
- /workflow:session:start "implement OAuth2 authentication"
|
||||
- /workflow:session:start "fix login bug"
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
---
|
||||
name: workflow-session-status
|
||||
name: status
|
||||
description: Show detailed status of active workflow session
|
||||
usage: /workflow:session:status
|
||||
parent: /workflow:session
|
||||
|
||||
---
|
||||
|
||||
# Workflow Session Status (/workflow:session:status)
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
---
|
||||
name: workflow-session-switch
|
||||
name: switch
|
||||
description: Switch to a different workflow session
|
||||
usage: /workflow:session:switch <session-id>
|
||||
parent: /workflow:session
|
||||
|
||||
examples:
|
||||
- /workflow:session:switch WFS-oauth-integration
|
||||
- /workflow:session:switch WFS-user-profile
|
||||
|
||||
273
.claude/scripts/medium-project-update.sh
Normal file
273
.claude/scripts/medium-project-update.sh
Normal file
@@ -0,0 +1,273 @@
|
||||
#!/bin/bash
|
||||
# medium-project-update.sh
|
||||
# Layered parallel execution for medium projects (50-200 files)
|
||||
# Emphasizes gemini CLI usage with direct file modification
|
||||
|
||||
set -e # Exit on any error
|
||||
|
||||
echo "🚀 === Medium Project Layered Analysis ==="
|
||||
echo "Project: $(pwd)"
|
||||
echo "Timestamp: $(date)"
|
||||
|
||||
# Function to check if directory exists and has files
|
||||
check_directory() {
|
||||
local dir=$1
|
||||
local pattern=$2
|
||||
if [ -d "$dir" ] && find "$dir" -type f $pattern -print -quit | grep -q .; then
|
||||
return 0
|
||||
else
|
||||
return 1
|
||||
fi
|
||||
}
|
||||
|
||||
# Function to run gemini with error handling
|
||||
run_gemini() {
|
||||
local cmd="$1"
|
||||
local desc="$2"
|
||||
echo " 📝 $desc"
|
||||
if ! eval "$cmd"; then
|
||||
echo " ❌ Failed: $desc"
|
||||
return 1
|
||||
else
|
||||
echo " ✅ Completed: $desc"
|
||||
return 0
|
||||
fi
|
||||
}
|
||||
|
||||
echo ""
|
||||
echo "🏗️ === Layer 1: Foundation modules (parallel) ==="
|
||||
echo "Analyzing base dependencies: types, utils, core..."
|
||||
(
|
||||
# Only run gemini commands for directories that exist
|
||||
if check_directory "src/types" "-name '*.ts' -o -name '*.js'"; then
|
||||
run_gemini "gemini -yolo -p '@{src/types/**/*}
|
||||
Analyze type definitions and interfaces. Update src/types/CLAUDE.md with:
|
||||
- Type architecture patterns
|
||||
- Interface design principles
|
||||
- Type safety guidelines
|
||||
- Usage examples'" "Type definitions analysis" &
|
||||
fi
|
||||
|
||||
if check_directory "src/utils" "-name '*.ts' -o -name '*.js' -o -name '*.py'"; then
|
||||
run_gemini "gemini -yolo -p '@{src/utils/**/*}
|
||||
Analyze utility functions and helpers. Update src/utils/CLAUDE.md with:
|
||||
- Utility function patterns
|
||||
- Helper library organization
|
||||
- Common functionality guidelines
|
||||
- Reusability principles'" "Utility functions analysis" &
|
||||
fi
|
||||
|
||||
if check_directory "src/core" "-name '*.ts' -o -name '*.js' -o -name '*.py'"; then
|
||||
run_gemini "gemini -yolo -p '@{src/core/**/*}
|
||||
Analyze core modules and system architecture. Update src/core/CLAUDE.md with:
|
||||
- Core system architecture
|
||||
- Module initialization patterns
|
||||
- System-wide configuration
|
||||
- Base class implementations'" "Core modules analysis" &
|
||||
fi
|
||||
|
||||
if check_directory "src/lib" "-name '*.ts' -o -name '*.js' -o -name '*.py'"; then
|
||||
run_gemini "gemini -yolo -p '@{src/lib/**/*}
|
||||
Analyze library modules and shared functionality. Update src/lib/CLAUDE.md with:
|
||||
- Shared library patterns
|
||||
- Cross-module utilities
|
||||
- External integrations
|
||||
- Library architecture'" "Library modules analysis" &
|
||||
fi
|
||||
|
||||
wait
|
||||
)
|
||||
|
||||
echo ""
|
||||
echo "🏭 === Layer 2: Business logic (parallel, depends on Layer 1) ==="
|
||||
echo "Analyzing business modules with foundation context..."
|
||||
(
|
||||
if check_directory "src/api" "-name '*.ts' -o -name '*.js' -o -name '*.py'"; then
|
||||
run_gemini "gemini -yolo -p '@{src/api/**/*} @{src/core/CLAUDE.md,src/types/CLAUDE.md}
|
||||
Analyze API endpoints and routes with core/types context. Update src/api/CLAUDE.md with:
|
||||
- API architecture patterns
|
||||
- Endpoint design principles
|
||||
- Request/response handling
|
||||
- Authentication integration
|
||||
- Error handling patterns'" "API endpoints analysis" &
|
||||
fi
|
||||
|
||||
if check_directory "src/services" "-name '*.ts' -o -name '*.js' -o -name '*.py'"; then
|
||||
run_gemini "gemini -yolo -p '@{src/services/**/*} @{src/utils/CLAUDE.md,src/types/CLAUDE.md}
|
||||
Analyze business services with utils/types context. Update src/services/CLAUDE.md with:
|
||||
- Service layer architecture
|
||||
- Business logic patterns
|
||||
- Data processing workflows
|
||||
- Service integration patterns
|
||||
- Dependency injection'" "Business services analysis" &
|
||||
fi
|
||||
|
||||
if check_directory "src/models" "-name '*.ts' -o -name '*.js' -o -name '*.py'"; then
|
||||
run_gemini "gemini -yolo -p '@{src/models/**/*} @{src/types/CLAUDE.md}
|
||||
Analyze data models with types context. Update src/models/CLAUDE.md with:
|
||||
- Data model architecture
|
||||
- Entity relationship patterns
|
||||
- Validation strategies
|
||||
- Model lifecycle management
|
||||
- Database integration'" "Data models analysis" &
|
||||
fi
|
||||
|
||||
if check_directory "src/database" "-name '*.ts' -o -name '*.js' -o -name '*.py'"; then
|
||||
run_gemini "gemini -yolo -p '@{src/database/**/*} @{src/models/CLAUDE.md,src/core/CLAUDE.md}
|
||||
Analyze database layer with models/core context. Update src/database/CLAUDE.md with:
|
||||
- Database architecture
|
||||
- Query optimization patterns
|
||||
- Migration strategies
|
||||
- Connection management
|
||||
- Data access patterns'" "Database layer analysis" &
|
||||
fi
|
||||
|
||||
wait
|
||||
)
|
||||
|
||||
echo ""
|
||||
echo "🎨 === Layer 3: Application layer (depends on Layer 2) ==="
|
||||
echo "Analyzing UI and application modules with business context..."
|
||||
(
|
||||
if check_directory "src/components" "-name '*.tsx' -o -name '*.jsx' -o -name '*.vue'"; then
|
||||
run_gemini "gemini -yolo -p '@{src/components/**/*} @{src/api/CLAUDE.md,src/services/CLAUDE.md}
|
||||
Analyze UI components with API/services context. Update src/components/CLAUDE.md with:
|
||||
- Component architecture patterns
|
||||
- State management strategies
|
||||
- Props and event handling
|
||||
- Component lifecycle patterns
|
||||
- Styling conventions'" "UI components analysis" &
|
||||
fi
|
||||
|
||||
if check_directory "src/pages" "-name '*.tsx' -o -name '*.jsx' -o -name '*.vue'"; then
|
||||
run_gemini "gemini -yolo -p '@{src/pages/**/*} @{src/services/CLAUDE.md,src/components/CLAUDE.md}
|
||||
Analyze page components with services/components context. Update src/pages/CLAUDE.md with:
|
||||
- Page architecture patterns
|
||||
- Route management
|
||||
- Data fetching strategies
|
||||
- Layout compositions
|
||||
- SEO considerations'" "Page components analysis" &
|
||||
fi
|
||||
|
||||
if check_directory "src/hooks" "-name '*.ts' -o -name '*.js'"; then
|
||||
run_gemini "gemini -yolo -p '@{src/hooks/**/*} @{src/services/CLAUDE.md}
|
||||
Analyze custom hooks with services context. Update src/hooks/CLAUDE.md with:
|
||||
- Custom hook patterns
|
||||
- State logic reusability
|
||||
- Effect management
|
||||
- Hook composition strategies
|
||||
- Performance considerations'" "Custom hooks analysis" &
|
||||
fi
|
||||
|
||||
if check_directory "src/styles" "-name '*.css' -o -name '*.scss' -o -name '*.less'"; then
|
||||
run_gemini "gemini -yolo -p '@{src/styles/**/*} @{src/components/CLAUDE.md}
|
||||
Analyze styling with components context. Update src/styles/CLAUDE.md with:
|
||||
- Styling architecture
|
||||
- CSS methodology
|
||||
- Theme management
|
||||
- Responsive design patterns
|
||||
- Design system integration'" "Styling analysis" &
|
||||
fi
|
||||
|
||||
wait
|
||||
)
|
||||
|
||||
echo ""
|
||||
echo "📋 === Layer 4: Supporting modules (parallel) ==="
|
||||
echo "Analyzing configuration, tests, and documentation..."
|
||||
(
|
||||
if check_directory "tests" "-name '*.test.*' -o -name '*.spec.*'"; then
|
||||
run_gemini "gemini -yolo -p '@{tests/**/*,**/*.test.*,**/*.spec.*}
|
||||
Analyze testing strategy and patterns. Update tests/CLAUDE.md with:
|
||||
- Testing architecture
|
||||
- Unit test patterns
|
||||
- Integration test strategies
|
||||
- Mocking and fixtures
|
||||
- Test data management
|
||||
- Coverage requirements'" "Testing strategy analysis" &
|
||||
fi
|
||||
|
||||
if check_directory "config" "-name '*.json' -o -name '*.js' -o -name '*.yaml'"; then
|
||||
run_gemini "gemini -yolo -p '@{config/**/*,*.config.*,.env*}
|
||||
Analyze configuration management. Update config/CLAUDE.md with:
|
||||
- Configuration architecture
|
||||
- Environment management
|
||||
- Secret handling patterns
|
||||
- Build configuration
|
||||
- Deployment settings'" "Configuration analysis" &
|
||||
fi
|
||||
|
||||
if check_directory "scripts" "-name '*.sh' -o -name '*.js' -o -name '*.py'"; then
|
||||
run_gemini "gemini -yolo -p '@{scripts/**/*}
|
||||
Analyze build and deployment scripts. Update scripts/CLAUDE.md with:
|
||||
- Build process documentation
|
||||
- Deployment workflows
|
||||
- Development scripts
|
||||
- Automation patterns
|
||||
- CI/CD integration'" "Scripts analysis" &
|
||||
fi
|
||||
|
||||
wait
|
||||
)
|
||||
|
||||
echo ""
|
||||
echo "🎯 === Layer 5: Root documentation integration ==="
|
||||
echo "Generating comprehensive root documentation..."
|
||||
|
||||
# Collect all existing CLAUDE.md files
|
||||
existing_docs=$(find . -name "CLAUDE.md" -path "*/src/*" | sort)
|
||||
if [ -n "$existing_docs" ]; then
|
||||
echo "Found module documentation:"
|
||||
echo "$existing_docs" | sed 's/^/ 📄 /'
|
||||
|
||||
run_gemini "gemini -yolo -p '@{src/*/CLAUDE.md,tests/CLAUDE.md,config/CLAUDE.md,scripts/CLAUDE.md} @{CLAUDE.md}
|
||||
Integrate all module documentation and update root CLAUDE.md with:
|
||||
|
||||
## Project Overview
|
||||
- Complete project architecture summary
|
||||
- Technology stack and dependencies
|
||||
- Module integration patterns
|
||||
- Development workflow and guidelines
|
||||
|
||||
## Architecture
|
||||
- System design principles
|
||||
- Module interdependencies
|
||||
- Data flow patterns
|
||||
- Key architectural decisions
|
||||
|
||||
## Development Guidelines
|
||||
- Coding standards and patterns
|
||||
- Testing strategies
|
||||
- Deployment procedures
|
||||
- Contribution guidelines
|
||||
|
||||
## Module Summary
|
||||
- Brief overview of each module's purpose
|
||||
- Key patterns and conventions
|
||||
- Integration points
|
||||
- Performance considerations
|
||||
|
||||
Focus on providing a comprehensive yet concise project overview that serves as the single source of truth for new developers.'" "Root documentation integration"
|
||||
else
|
||||
echo "⚠️ No module documentation found, generating basic root documentation..."
|
||||
run_gemini "gemini -yolo -p '@{**/*} @{CLAUDE.md}
|
||||
Generate comprehensive root CLAUDE.md documentation with:
|
||||
- Project overview and architecture
|
||||
- Technology stack summary
|
||||
- Development guidelines
|
||||
- Key patterns and conventions'" "Basic root documentation"
|
||||
fi
|
||||
|
||||
echo ""
|
||||
echo "✅ === Medium project update completed ==="
|
||||
echo "📊 Summary:"
|
||||
echo " - Layered analysis completed in dependency order"
|
||||
echo " - All gemini commands executed with -yolo for direct file modification"
|
||||
echo " - Module-specific CLAUDE.md files updated with contextual information"
|
||||
echo " - Root documentation integrated with complete project overview"
|
||||
echo " - Timestamp: $(date)"
|
||||
|
||||
# Optional: Show generated documentation structure
|
||||
echo ""
|
||||
echo "📁 Generated documentation structure:"
|
||||
find . -name "CLAUDE.md" | sort | sed 's/^/ 📄 /'
|
||||
Reference in New Issue
Block a user