claude-code-workflow 6.0.5 → 6.1.1

package/.claude/workflows/context-search-strategy.md

@@ -1,77 +1,77 @@
----
-name: context-search-strategy
-description: Strategic guidelines for context search commands
-type: search-guideline
----
-
-# Context Search Strategy
-
-## ⚡ Execution Environment
-
-**CRITICAL**: All commands execute in **Bash environment** (Git Bash on Windows)
-
-**❌ Forbidden**: Windows commands (`findstr`, `dir`, `where`) - Use Bash (`grep`, `find`, `cat`)
-
-## ⚡ Core Search Tools
-
-**Skill()**: FASTEST way to get context - use FIRST if SKILL exists. Three types: (1) `workflow-progress` for WFS sessions (2) tech SKILLs for stack docs (3) `{project-name}` for project docs
-**codebase-retrieval**: Semantic file discovery via Gemini CLI with all files analysis
-**rg (ripgrep)**: Fast content search with regex support
-**find**: File/directory location by name patterns
-**grep**: Built-in pattern matching (fallback when rg unavailable)
-**get_modules_by_depth.sh**: Program architecture analysis (MANDATORY before planning)
-
-## 📋 Tool Selection Matrix
-
-| Need | Tool | Use Case |
-|------|------|----------|
-| **Workflow history** | Skill(workflow-progress) | WFS sessions lessons/conflicts - `/memory:workflow-skill-memory` |
-| **Tech stack docs** | Skill({tech-name}) | Stack APIs/guides - `/memory:tech-research` |
-| **Project docs** | Skill({project-name}) | Project modules/architecture - `/memory:skill-memory` |
-| **Semantic discovery** | codebase-retrieval | Find files relevant to task/feature context |
-| **Pattern matching** | rg | Search code content with regex |
-| **File name lookup** | find | Locate files by name patterns |
-| **Architecture** | get_modules_by_depth.sh | Understand program structure |
-
-## 🔧 Quick Command Reference
-
-```bash
-# SKILL Packages (FIRST PRIORITY - fastest context loading)
-Skill(command: "workflow-progress")  # Workflow: WFS sessions history, lessons, conflicts
-Skill(command: "react-dev")          # Tech: React APIs, patterns, best practices
-Skill(command: "claude_dms3")        # Project: Project modules, architecture, examples
-
-# Semantic File Discovery (codebase-retrieval)
-cd [directory] && gemini -p "
-PURPOSE: Discover files relevant to task/feature
-TASK: List all files related to [task/feature description]
-MODE: analysis
-CONTEXT: @**/*
-EXPECTED: Relevant file paths with relevance explanation
-RULES: Focus on direct relevance to task requirements
-"
-
-# Program Architecture (MANDATORY before planning)
-~/.claude/scripts/get_modules_by_depth.sh
-
-# Content Search (rg preferred)
-rg "pattern" --type js -n        # Search JS files with line numbers
-rg -i "case-insensitive"         # Ignore case
-rg -C 3 "context"                # Show 3 lines before/after
-
-# File Search
-find . -name "*.ts" -type f      # Find TypeScript files
-find . -path "*/node_modules" -prune -o -name "*.js" -print
-
-# Workflow Examples
-rg "IMPL-\d+" .workflow/ --type json                    # Find task IDs
-find .workflow/ -name "*.json" -path "*/.task/*"        # Locate task files
-rg "status.*pending" .workflow/.task/                   # Find pending tasks
-```
-
-## ⚡ Performance Tips
-
-- **rg > grep** for content search
-- **Use --type filters** to limit file types
-- **Exclude dirs**: `--glob '!node_modules'`
-- **Use -F** for literal strings (no regex)
+---
+name: context-search-strategy
+description: Strategic guidelines for context search commands
+type: search-guideline
+---
+
+# Context Search Strategy
+
+## ⚡ Execution Environment
+
+**CRITICAL**: All commands execute in **Bash environment** (Git Bash on Windows)
+
+**❌ Forbidden**: Windows commands (`findstr`, `dir`, `where`) - Use Bash (`grep`, `find`, `cat`)
+
+## ⚡ Core Search Tools
+
+**Skill()**: FASTEST way to get context - use FIRST if SKILL exists. Three types: (1) `workflow-progress` for WFS sessions (2) tech SKILLs for stack docs (3) `{project-name}` for project docs
+**codebase-retrieval**: Semantic file discovery via Gemini CLI with all files analysis
+**rg (ripgrep)**: Fast content search with regex support
+**find**: File/directory location by name patterns
+**grep**: Built-in pattern matching (fallback when rg unavailable)
+**get_modules_by_depth.sh**: Program architecture analysis (MANDATORY before planning)
+
+## 📋 Tool Selection Matrix
+
+| Need | Tool | Use Case |
+|------|------|----------|
+| **Workflow history** | Skill(workflow-progress) | WFS sessions lessons/conflicts - `/memory:workflow-skill-memory` |
+| **Tech stack docs** | Skill({tech-name}) | Stack APIs/guides - `/memory:tech-research` |
+| **Project docs** | Skill({project-name}) | Project modules/architecture - `/memory:skill-memory` |
+| **Semantic discovery** | codebase-retrieval | Find files relevant to task/feature context |
+| **Pattern matching** | rg | Search code content with regex |
+| **File name lookup** | find | Locate files by name patterns |
+| **Architecture** | get_modules_by_depth.sh | Understand program structure |
+
+## 🔧 Quick Command Reference
+
+```bash
+# SKILL Packages (FIRST PRIORITY - fastest context loading)
+Skill(command: "workflow-progress")  # Workflow: WFS sessions history, lessons, conflicts
+Skill(command: "react-dev")          # Tech: React APIs, patterns, best practices
+Skill(command: "claude_dms3")        # Project: Project modules, architecture, examples
+
+# Semantic File Discovery (codebase-retrieval)
+cd [directory] && gemini -p "
+PURPOSE: Discover files relevant to task/feature
+TASK: List all files related to [task/feature description]
+MODE: analysis
+CONTEXT: @**/*
+EXPECTED: Relevant file paths with relevance explanation
+RULES: Focus on direct relevance to task requirements
+"
+
+# Program Architecture (MANDATORY before planning)
+ccw tool exec get_modules_by_depth '{}'
+
+# Content Search (rg preferred)
+rg "pattern" --type js -n        # Search JS files with line numbers
+rg -i "case-insensitive"         # Ignore case
+rg -C 3 "context"                # Show 3 lines before/after
+
+# File Search
+find . -name "*.ts" -type f      # Find TypeScript files
+find . -path "*/node_modules" -prune -o -name "*.js" -print
+
+# Workflow Examples
+rg "IMPL-\d+" .workflow/ --type json                    # Find task IDs
+find .workflow/ -name "*.json" -path "*/.task/*"        # Locate task files
+rg "status.*pending" .workflow/.task/                   # Find pending tasks
+```
+
+## ⚡ Performance Tips
+
+- **rg > grep** for content search
+- **Use --type filters** to limit file types
+- **Exclude dirs**: `--glob '!node_modules'`
+- **Use -F** for literal strings (no regex)

package/.claude/workflows/tool-strategy.md

@@ -1,71 +1,90 @@
-# Tool Strategy
-
-## ⚡ Exa Triggering Mechanisms
-
-**Auto-Trigger**:
-- User mentions "exa-code" or code-related queries → `mcp__exa__get_code_context_exa`
-- Need current web information → `mcp__exa__web_search_exa`
-
-**Manual Trigger**:
-- Complex API research → Exa Code Context
-- Real-time information needs → Exa Web Search
-
-## ⚡ Bash Text Processing (sed/awk)
-
-**When to Use**: Edit tool fails 2+ times on same file
-
-### sed Quick Reference
-
-```bash
-# Replace first occurrence per line
-sed 's/old/new/' file.txt
-
-# Replace all occurrences (global)
-sed 's/old/new/g' file.txt
-
-# In-place edit (modify file directly)
-sed -i 's/old/new/g' file.txt
-
-# Delete lines matching pattern
-sed '/pattern/d' file.txt
-
-# Insert line before match
-sed '/pattern/i\new line' file.txt
-
-# Insert line after match
-sed '/pattern/a\new line' file.txt
-
-# Replace on specific line number
-sed '5s/old/new/' file.txt
-
-# Multi-line replacement (escape newlines)
-sed ':a;N;$!ba;s/old\npattern/new\ntext/g' file.txt
-```
-
-### awk Quick Reference
-
-```bash
-# Print specific column
-awk '{print $1}' file.txt
-
-# Print lines matching pattern
-awk '/pattern/' file.txt
-
-# Replace field value
-awk '{$2="new"; print}' file.txt
-
-# Conditional replacement
-awk '/pattern/{gsub(/old/,"new")}1' file.txt
-
-# Insert line after match
-awk '/pattern/{print; print "new line"; next}1' file.txt
-
-# Multi-field operations
-awk -F',' '{print $1, $3}' file.csv
-```
-
-### Fallback Strategy
-
-1. **Edit fails 2+ times** → Try sed for simple replacements
-2. **sed fails** → Try awk for complex patterns
-3. **awk fails** → Use Write to recreate file
+# Tool Strategy
+
+## ⚡ Exa Triggering Mechanisms
+
+**Auto-Trigger**:
+- User mentions "exa-code" or code-related queries → `mcp__exa__get_code_context_exa`
+- Need current web information → `mcp__exa__web_search_exa`
+
+**Manual Trigger**:
+- Complex API research → Exa Code Context
+- Real-time information needs → Exa Web Search
+
+## ⚡ CCW edit_file Tool (AI-Powered Editing)
+
+**When to Use**: Edit tool fails 2+ times on same file
+
+### update Mode (Default)
+
+**Best for**: Code block replacements, function rewrites, multi-line changes
+
+```bash
+ccw tool exec edit_file '{
+  "path": "file.py",
+  "oldText": "def old():\n    pass",
+  "newText": "def new():\n    return True"
+}'
+```
+
+**Features**:
+- ✅ Exact text matching (precise and predictable)
+- ✅ Auto line ending adaptation (CRLF/LF)
+- ✅ Simple `oldText` → `newText` replacement
+- ✅ No special markers needed
+
+### line Mode (Precise Line Operations)
+
+**Best for**: Config files, line insertions/deletions, precise line number control
+
+```bash
+# Insert after specific line
+ccw tool exec edit_file '{
+  "path": "config.txt",
+  "mode": "line",
+  "operation": "insert_after",
+  "line": 10,
+  "text": "new config line"
+}'
+
+# Delete line range
+ccw tool exec edit_file '{
+  "path": "log.txt",
+  "mode": "line",
+  "operation": "delete",
+  "line": 5,
+  "end_line": 8
+}'
+
+# Replace specific line
+ccw tool exec edit_file '{
+  "path": "script.sh",
+  "mode": "line",
+  "operation": "replace",
+  "line": 3,
+  "text": "#!/bin/bash"
+}'
+```
+
+**Operations**:
+- `insert_before`: Insert text before specified line
+- `insert_after`: Insert text after specified line
+- `replace`: Replace line or line range
+- `delete`: Delete line or line range
+
+### Mode Selection Guide
+
+| Scenario | Mode | Reason |
+|----------|------|--------|
+| Code refactoring | update | Content-driven replacement |
+| Function rewrite | update | Simple oldText/newText |
+| Config line change | line | Precise line number control |
+| Insert at specific position | line | Exact line number needed |
+| Delete line range | line | Line-based operation |
+
+### Fallback Strategy
+
+1. **Edit fails 1+ times** → Use `ccw tool exec edit_file` (update mode)
+2. **update mode fails** → Try line mode with precise line numbers
+3. **All fails** → Use Write to recreate file
+
+**Default mode**: update (exact matching with line ending adaptation)

package/.claude/workflows/workflow-architecture.md

@@ -433,7 +433,7 @@ The `[FLOW_CONTROL]` marker indicates that a task or prompt contains flow contro
   "step": "load_context",
   "action": "Load project context and patterns",
   "commands": [
-    "bash(~/.claude/scripts/get_modules_by_depth.sh)",
+    "bash(ccw tool exec get_modules_by_depth '{}')",
     "Read(CLAUDE.md)"
   ],
   "output_to": "project_structure",