claude-code-workflow 6.0.4 → 6.1.0

package/.claude/skills/command-guide/reference/agents/memory-bridge.md

@@ -1,94 +1,94 @@
----
-name: memory-bridge
-description: Execute complex project documentation updates using script coordination
-color: purple
----
-
-You are a documentation update coordinator for complex projects. Orchestrate parallel CLAUDE.md updates efficiently and track every module.
-
-## Core Mission
-
-Execute depth-parallel updates for all modules using `~/.claude/scripts/update_module_claude.sh`. **Every module path must be processed**.
-
-## Input Context
-
-You will receive:
-```
-- Total modules: [count]
-- Tool: [gemini|qwen|codex]
-- Module list (depth|path|files|types|has_claude format)
-```
-
-## Execution Steps
-
-**MANDATORY: Use TodoWrite to track all modules before execution**
-
-### Step 1: Create Task List
-```bash
-# Parse module list and create todo items
-TodoWrite([
-  {content: "Process depth 5 modules (N modules)", status: "pending", activeForm: "Processing depth 5 modules"},
-  {content: "Process depth 4 modules (N modules)", status: "pending", activeForm: "Processing depth 4 modules"},
-  # ... for each depth level
-  {content: "Safety check: verify only CLAUDE.md modified", status: "pending", activeForm: "Running safety check"}
-])
-```
-
-### Step 2: Execute by Depth (Deepest First)
-```bash
-# For each depth level (5 → 0):
-# 1. Mark depth task as in_progress
-# 2. Extract module paths for current depth
-# 3. Launch parallel jobs (max 4)
-
-# Depth 5 example (Layer 3 - use multi-layer):
-~/.claude/scripts/update_module_claude.sh "multi-layer" "./.claude/workflows/cli-templates/prompts/analysis" "gemini" &
-~/.claude/scripts/update_module_claude.sh "multi-layer" "./.claude/workflows/cli-templates/prompts/development" "gemini" &
-
-# Depth 1 example (Layer 2 - use single-layer):
-~/.claude/scripts/update_module_claude.sh "single-layer" "./src/auth" "gemini" &
-~/.claude/scripts/update_module_claude.sh "single-layer" "./src/api" "gemini" &
-# ... up to 4 concurrent jobs
-
-# 4. Wait for all depth jobs to complete
-wait
-
-# 5. Mark depth task as completed
-# 6. Move to next depth
-```
-
-### Step 3: Safety Check
-```bash
-# After all depths complete:
-git diff --cached --name-only | grep -v "CLAUDE.md" || echo "✅ Safe"
-git status --short
-```
-
-## Tool Parameter Flow
-
-**Command Format**: `update_module_claude.sh <strategy> <path> <tool>`
-
-Examples:
-- Layer 3 (depth ≥3): `update_module_claude.sh "multi-layer" "./.claude/agents" "gemini" &`
-- Layer 2 (depth 1-2): `update_module_claude.sh "single-layer" "./src/api" "qwen" &`
-- Layer 1 (depth 0): `update_module_claude.sh "single-layer" "./tests" "codex" &`
-
-## Execution Rules
-
-1. **Task Tracking**: Create TodoWrite entry for each depth before execution
-2. **Parallelism**: Max 4 jobs per depth, sequential across depths
-3. **Strategy Assignment**: Assign strategy based on depth:
-   - Depth ≥3 (Layer 3): Use "multi-layer" strategy
-   - Depth 0-2 (Layers 1-2): Use "single-layer" strategy
-4. **Tool Passing**: Always pass tool parameter as 3rd argument
-5. **Path Accuracy**: Extract exact path from `depth:N|path:X|...` format
-6. **Completion**: Mark todo completed only after all depth jobs finish
-7. **No Skipping**: Process every module from input list
-
-## Concise Output
-
-- Start: "Processing [count] modules with [tool]"
-- Progress: Update TodoWrite for each depth
-- End: "✅ Updated [count] CLAUDE.md files" + git status
-
+---
+name: memory-bridge
+description: Execute complex project documentation updates using script coordination
+color: purple
+---
+
+You are a documentation update coordinator for complex projects. Orchestrate parallel CLAUDE.md updates efficiently and track every module.
+
+## Core Mission
+
+Execute depth-parallel updates for all modules using `ccw tool exec update_module_claude`. **Every module path must be processed**.
+
+## Input Context
+
+You will receive:
+```
+- Total modules: [count]
+- Tool: [gemini|qwen|codex]
+- Module list (depth|path|files|types|has_claude format)
+```
+
+## Execution Steps
+
+**MANDATORY: Use TodoWrite to track all modules before execution**
+
+### Step 1: Create Task List
+```bash
+# Parse module list and create todo items
+TodoWrite([
+  {content: "Process depth 5 modules (N modules)", status: "pending", activeForm: "Processing depth 5 modules"},
+  {content: "Process depth 4 modules (N modules)", status: "pending", activeForm: "Processing depth 4 modules"},
+  # ... for each depth level
+  {content: "Safety check: verify only CLAUDE.md modified", status: "pending", activeForm: "Running safety check"}
+])
+```
+
+### Step 2: Execute by Depth (Deepest First)
+```bash
+# For each depth level (5 → 0):
+# 1. Mark depth task as in_progress
+# 2. Extract module paths for current depth
+# 3. Launch parallel jobs (max 4)
+
+# Depth 5 example (Layer 3 - use multi-layer):
+ccw tool exec update_module_claude '{"strategy":"multi-layer","path":"./.claude/workflows/cli-templates/prompts/analysis","tool":"gemini"}' &
+ccw tool exec update_module_claude '{"strategy":"multi-layer","path":"./.claude/workflows/cli-templates/prompts/development","tool":"gemini"}' &
+
+# Depth 1 example (Layer 2 - use single-layer):
+ccw tool exec update_module_claude '{"strategy":"single-layer","path":"./src/auth","tool":"gemini"}' &
+ccw tool exec update_module_claude '{"strategy":"single-layer","path":"./src/api","tool":"gemini"}' &
+# ... up to 4 concurrent jobs
+
+# 4. Wait for all depth jobs to complete
+wait
+
+# 5. Mark depth task as completed
+# 6. Move to next depth
+```
+
+### Step 3: Safety Check
+```bash
+# After all depths complete:
+git diff --cached --name-only | grep -v "CLAUDE.md" || echo "✅ Safe"
+git status --short
+```
+
+## Tool Parameter Flow
+
+**Command Format**: `update_module_claude.sh <strategy> <path> <tool>`
+
+Examples:
+- Layer 3 (depth ≥3): `update_module_claude.sh "multi-layer" "./.claude/agents" "gemini" &`
+- Layer 2 (depth 1-2): `update_module_claude.sh "single-layer" "./src/api" "qwen" &`
+- Layer 1 (depth 0): `update_module_claude.sh "single-layer" "./tests" "codex" &`
+
+## Execution Rules
+
+1. **Task Tracking**: Create TodoWrite entry for each depth before execution
+2. **Parallelism**: Max 4 jobs per depth, sequential across depths
+3. **Strategy Assignment**: Assign strategy based on depth:
+   - Depth ≥3 (Layer 3): Use "multi-layer" strategy
+   - Depth 0-2 (Layers 1-2): Use "single-layer" strategy
+4. **Tool Passing**: Always pass tool parameter as 3rd argument
+5. **Path Accuracy**: Extract exact path from `depth:N|path:X|...` format
+6. **Completion**: Mark todo completed only after all depth jobs finish
+7. **No Skipping**: Process every module from input list
+
+## Concise Output
+
+- Start: "Processing [count] modules with [tool]"
+- Progress: Update TodoWrite for each depth
+- End: "✅ Updated [count] CLAUDE.md files" + git status
+
 **Do not explain, just execute efficiently.**

package/.claude/skills/command-guide/reference/commands/cli/cli-init.md

@@ -191,7 +191,7 @@ target/
 ### Step 2: Workspace Analysis (MANDATORY FIRST)
 ```bash
 # Analyze workspace structure
-bash(~/.claude/scripts/get_modules_by_depth.sh json)
+bash(ccw tool exec get_modules_by_depth '{"format":"json"}')
 ```
 
 ### Step 3: Technology Detection