claude-code-workflow 6.1.4 → 6.2.1

package/.claude/commands/memory/load-skill-memory.md

@@ -1,182 +0,0 @@
----
-name: load-skill-memory
-description: Activate SKILL package (auto-detect from paths/keywords or manual) and intelligently load documentation based on task intent keywords
-argument-hint: "[skill_name] \"task intent description\""
-allowed-tools: Bash(*), Read(*), Skill(*)
----
-
-# Memory Load SKILL Command (/memory:load-skill-memory)
-
-## 1. Overview
-
-The `memory:load-skill-memory` command **activates SKILL package** (auto-detect from task or manual specification) and intelligently loads documentation based on user's task intent. The system automatically determines which documentation files to read based on the intent description.
-
-**Core Philosophy**:
-- **Flexible Activation**: Auto-detect skill from task description/paths, or user explicitly specifies
-- **Intent-Driven Loading**: System analyzes task intent to determine documentation scope
-- **Intelligent Selection**: Automatically chooses appropriate documentation level and modules
-- **Direct Context Loading**: Loads selected documentation into conversation memory
-
-**When to Use**:
-- Manually activate a known SKILL package for a specific task
-- Load SKILL context when system hasn't auto-triggered it
-- Force reload SKILL documentation with specific intent focus
-
-**Note**: Normal SKILL activation happens automatically via description triggers or path mentions (system extracts skill name from file paths for intelligent triggering). Use this command only when manual activation is needed.
-
-## 2. Parameters
-
-- `[skill_name]` (Optional): Name of SKILL package to activate
-  - If omitted: System auto-detects from task description or file paths
-  - If specified: Direct activation of named SKILL package
-  - Example: `my_project`, `api_service`
-  - Must match directory name under `.claude/skills/`
-
-- `"task intent description"` (Required): Description of what you want to do
-  - Used for both: auto-detection (if skill_name omitted) and documentation scope selection
-  - **Analysis tasks**: "分析builder pattern实现", "理解参数系统架构"
-  - **Modification tasks**: "修改workflow逻辑", "增强thermal template功能"
-  - **Learning tasks**: "学习接口设计模式", "了解测试框架使用"
-  - **With paths**: "修改D:\projects\my_project\src\auth.py的认证逻辑" (auto-extracts `my_project`)
-
-## 3. Execution Flow
-
-### Step 1: Determine SKILL Name (if not provided)
-
-**Auto-Detection Strategy** (when skill_name parameter is omitted):
-1. **Path Extraction**: Scan task description for file paths
-   - Extract potential project names from path segments
-   - Example: `"修改D:\projects\my_project\src\auth.py"` → extracts `my_project`
-2. **Keyword Matching**: Match task keywords against SKILL descriptions
-   - Search for project-specific terms, domain keywords
-3. **Validation**: Check if extracted name matches `.claude/skills/{skill_name}/`
-
-**Result**: Either uses provided skill_name or auto-detected name for activation
-
-### Step 2: Activate SKILL and Analyze Intent
-
-**Activate SKILL Package**:
-```javascript
-Skill(command: "${skill_name}")  // Uses provided or auto-detected name
-```
-
-**What Happens After Activation**:
-1. If SKILL exists in memory: System reads `.claude/skills/${skill_name}/SKILL.md`
-2. If SKILL not found in memory: Error - SKILL package doesn't exist
-3. SKILL description triggers are loaded into memory
-4. Progressive loading mechanism becomes available
-5. Documentation structure is now accessible
-
-**Intent Analysis**:
-Based on task intent description, system determines:
-- **Action type**: analyzing, modifying, learning
-- **Scope**: specific module, architecture overview, complete system
-- **Depth**: quick reference, detailed API, full documentation
-
-### Step 3: Intelligent Documentation Loading
-
-**Loading Strategy**:
-
-The system automatically selects documentation based on intent keywords:
-
-1. **Quick Understanding** ("了解", "快速理解", "什么是"):
-   - Load: Level 0 (README.md only, ~2K tokens)
-   - Use case: Quick overview of capabilities
-
-2. **Specific Module Analysis** ("分析XXX模块", "理解XXX实现"):
-   - Load: Module-specific README.md + API.md (~5K tokens)
-   - Use case: Deep dive into specific component
-
-3. **Architecture Review** ("架构", "设计模式", "整体结构"):
-   - Load: README.md + ARCHITECTURE.md (~10K tokens)
-   - Use case: System design understanding
-
-4. **Implementation/Modification** ("修改", "增强", "实现"):
-   - Load: Relevant module docs + EXAMPLES.md (~15K tokens)
-   - Use case: Code modification with examples
-
-5. **Comprehensive Learning** ("学习", "完整了解", "深入理解"):
-   - Load: Level 3 (All documentation, ~40K tokens)
-   - Use case: Complete system mastery
-
-**Documentation Loaded into Memory**:
-After loading, the selected documentation content is available in conversation memory for subsequent operations.
-
-## 4. Usage Examples
-
-### Example 1: Manual Specification
-
-**User Command**:
-```bash
-/memory:load-skill-memory my_project "修改认证模块增加OAuth支持"
-```
-
-**Execution**:
-```javascript
-// Step 1: Use provided skill_name
-skill_name = "my_project"  // Directly from parameter
-
-// Step 2: Activate SKILL
-Skill(command: "my_project")
-
-// Step 3: Intent Analysis
-Keywords: ["修改", "认证模块", "增加", "OAuth"]
-Action: modifying (implementation)
-Scope: auth module + examples
-
-// Load documentation based on intent
-Read(.workflow/docs/my_project/auth/README.md)
-Read(.workflow/docs/my_project/auth/API.md)
-Read(.workflow/docs/my_project/EXAMPLES.md)
-```
-
-### Example 2: Auto-Detection from Path
-
-**User Command**:
-```bash
-/memory:load-skill-memory "修改D:\projects\my_project\src\services\api.py的接口逻辑"
-```
-
-**Execution**:
-```javascript
-// Step 1: Auto-detect skill_name from path
-Path detected: "D:\projects\my_project\src\services\api.py"
-Extracted: "my_project"
-Validated: .claude/skills/my_project/ exists ✓
-skill_name = "my_project"
-
-// Step 2: Activate SKILL
-Skill(command: "my_project")
-
-// Step 3: Intent Analysis
-Keywords: ["修改", "services", "接口逻辑"]
-Action: modifying (implementation)
-Scope: services module + examples
-
-// Load documentation based on intent
-Read(.workflow/docs/my_project/services/README.md)
-Read(.workflow/docs/my_project/services/API.md)
-Read(.workflow/docs/my_project/EXAMPLES.md)
-```
-
-## 5. Intent Keyword Mapping
-
-**Quick Reference**:
-- **Triggers**: "了解", "快速", "什么是", "简介"
-- **Loads**: README.md only (~2K)
-
-**Module-Specific**:
-- **Triggers**: "XXX模块", "XXX组件", "分析XXX"
-- **Loads**: Module README + API (~5K)
-
-**Architecture**:
-- **Triggers**: "架构", "设计", "整体结构", "系统设计"
-- **Loads**: README + ARCHITECTURE (~10K)
-
-**Implementation**:
-- **Triggers**: "修改", "增强", "实现", "开发", "集成"
-- **Loads**: Relevant module + EXAMPLES (~15K)
-
-**Comprehensive**:
-- **Triggers**: "完整", "深入", "全面", "学习整个"
-- **Loads**: All documentation (~40K)

package/.claude/commands/memory/load.md

@@ -1,240 +0,0 @@
----
-name: load
-description: Delegate to universal-executor agent to analyze project via Gemini/Qwen CLI and return JSON core content package for task context
-argument-hint: "[--tool gemini|qwen] \"task context description\""
-allowed-tools: Task(*), Bash(*)
-examples:
-  - /memory:load "在当前前端基础上开发用户认证功能"
-  - /memory:load --tool qwen -p "重构支付模块API"
----
-
-# Memory Load Command (/memory:load)
-
-## 1. Overview
-
-The `memory:load` command **delegates to a universal-executor agent** to analyze the project and return a structured "Core Content Pack". This pack is loaded into the main thread's memory, providing essential context for subsequent agent operations while minimizing token consumption.
-
-**Core Philosophy**:
-- **Agent-Driven**: Fully delegates execution to universal-executor agent
-- **Read-Only Analysis**: Does not modify code, only extracts context
-- **Structured Output**: Returns standardized JSON content package
-- **Memory Optimization**: Package loaded directly into main thread memory
-- **Token Efficiency**: CLI analysis executed within agent to save tokens
-
-## 2. Parameters
-
-- `"task context description"` (Required): Task description to guide context extraction
-  - Example: "在当前前端基础上开发用户认证功能"
-  - Example: "重构支付模块API"
-  - Example: "修复数据库查询性能问题"
-
-- `--tool <gemini|qwen>` (Optional): Specify CLI tool for agent to use (default: gemini)
-  - gemini: Large context window, suitable for complex project analysis
-  - qwen: Alternative to Gemini with similar capabilities
-
-## 3. Agent-Driven Execution Flow
-
-The command fully delegates to **universal-executor agent**, which autonomously:
-
-1. **Analyzes Project Structure**: Executes `get_modules_by_depth.sh` to understand architecture
-2. **Loads Documentation**: Reads CLAUDE.md, README.md and other key docs
-3. **Extracts Keywords**: Derives core keywords from task description
-4. **Discovers Files**: Uses MCP code-index or rg/find to locate relevant files
-5. **CLI Deep Analysis**: Executes Gemini/Qwen CLI for deep context analysis
-6. **Generates Content Package**: Returns structured JSON core content package
-
-## 4. Core Content Package Structure
-
-**Output Format** - Loaded into main thread memory for subsequent use:
-
-```json
-{
-  "task_context": "在当前前端基础上开发用户认证功能",
-  "keywords": ["前端", "用户", "认证", "auth", "login"],
-  "project_summary": {
-    "architecture": "TypeScript + React frontend with Vite build system",
-    "tech_stack": ["React", "TypeScript", "Vite", "TailwindCSS"],
-    "key_patterns": [
-      "State management via Context API",
-      "Functional components with Hooks pattern",
-      "API calls encapsulated in custom hooks"
-    ]
-  },
-  "relevant_files": [
-    {
-      "path": "src/components/Auth/LoginForm.tsx",
-      "relevance": "Existing login form component",
-      "priority": "high"
-    },
-    {
-      "path": "src/contexts/AuthContext.tsx",
-      "relevance": "Authentication state management context",
-      "priority": "high"
-    },
-    {
-      "path": "CLAUDE.md",
-      "relevance": "Project development standards",
-      "priority": "high"
-    }
-  ],
-  "integration_points": [
-    "Must integrate with existing AuthContext",
-    "Follow component organization pattern: src/components/[Feature]/",
-    "API calls should use src/hooks/useApi.ts wrapper"
-  ],
-  "constraints": [
-    "Maintain backward compatibility",
-    "Follow TypeScript strict mode",
-    "Use existing UI component library"
-  ]
-}
-```
-
-## 5. Agent Invocation
-
-```javascript
-Task(
-  subagent_type="universal-executor",
-  description="Load project memory: ${task_description}",
-  prompt=`
-## Mission: Load Project Memory Context
-
-**Task**: Load project memory context for: "${task_description}"
-**Mode**: analysis
-**Tool Preference**: ${tool || 'gemini'}
-
-## Execution Steps
-
-### Step 1: Foundation Analysis
-
-1. **Project Structure**
-   \`\`\`bash
-   bash(ccw tool exec get_modules_by_depth '{}')
-   \`\`\`
-
-2. **Core Documentation**
-   \`\`\`javascript
-   Read(CLAUDE.md)
-   Read(README.md)
-   \`\`\`
-
-### Step 2: Keyword Extraction & File Discovery
-
-1. Extract core keywords from task description
-2. Discover relevant files using ripgrep and find:
-   \`\`\`bash
-   # Find files by name
-   find . -name "*{keyword}*" -type f
-
-   # Search content with ripgrep
-   rg "{keyword}" --type ts --type md -C 2
-   rg -l "{keyword}" --type ts --type md  # List files only
-   \`\`\`
-
-### Step 3: Deep Analysis via CLI
-
-Execute Gemini/Qwen CLI for deep analysis (saves main thread tokens):
-
-\`\`\`bash
-cd . && ${tool} -p "
-PURPOSE: Extract project core context for task: ${task_description}
-TASK: Analyze project architecture, tech stack, key patterns, relevant files
-MODE: analysis
-CONTEXT: @CLAUDE.md,README.md @${discovered_files}
-EXPECTED: Structured project summary and integration point analysis
-RULES:
-- Focus on task-relevant core information
-- Identify key architecture patterns and technical constraints
-- Extract integration points and development standards
-- Output concise, structured format
-"
-\`\`\`
-
-### Step 4: Generate Core Content Package
-
-Generate structured JSON content package (format shown above)
-
-**Required Fields**:
-- task_context: Original task description
-- keywords: Extracted keyword array
-- project_summary: Architecture, tech stack, key patterns
-- relevant_files: File list with path, relevance, priority
-- integration_points: Integration guidance
-- constraints: Development constraints
-
-### Step 5: Return Content Package
-
-Return JSON content package as final output for main thread to load into memory.
-
-## Quality Checklist
-
-Before returning:
-- [ ] Valid JSON format
-- [ ] All required fields complete
-- [ ] relevant_files contains 3-10 files minimum
-- [ ] project_summary accurately reflects architecture
-- [ ] integration_points clearly specify integration paths
-- [ ] keywords accurately extracted (3-8 keywords)
-- [ ] Content concise, avoiding redundancy (< 5KB total)
-
-  `
-)
-```
-
-## 6. Usage Examples
-
-### Example 1: Load Context for New Feature
-
-```bash
-/memory:load "在当前前端基础上开发用户认证功能"
-```
-
-**Agent Execution**:
-1. Analyzes project structure (`get_modules_by_depth.sh`)
-2. Reads CLAUDE.md, README.md
-3. Extracts keywords: ["前端", "用户", "认证", "auth"]
-4. Uses MCP to search relevant files
-5. Executes Gemini CLI for deep analysis
-6. Returns core content package
-
-**Returned Package** (loaded into memory):
-```json
-{
-  "task_context": "在当前前端基础上开发用户认证功能",
-  "keywords": ["前端", "认证", "auth", "login"],
-  "project_summary": { ... },
-  "relevant_files": [ ... ],
-  "integration_points": [ ... ],
-  "constraints": [ ... ]
-}
-```
-
-### Example 2: Using Qwen Tool
-
-```bash
-/memory:load --tool qwen -p "重构支付模块API"
-```
-
-Agent uses Qwen CLI for analysis, returns same structured package.
-
-### Example 3: Bug Fix Context
-
-```bash
-/memory:load "修复登录验证错误"
-```
-
-Returns core context related to login validation, including test files and validation logic.
-
-### Memory Persistence
-
-- **Session-Scoped**: Content package valid for current session
-- **Subsequent Reference**: All subsequent agents/commands can access
-- **Reload Required**: New sessions need to re-execute /memory:load
-
-## 8. Notes
-
-- **Read-Only**: Does not modify any code, pure analysis
-- **Token Optimization**: CLI analysis executed within agent, saves main thread tokens
-- **Memory Loading**: Returned JSON loaded directly into main thread memory
-- **Subsequent Use**: Other commands/agents can reference this package for development
-- **Session-Level**: Content package valid for current session