ccg-workflow 1.0.0

package/templates/commands/think.md

@@ -0,0 +1,73 @@
+---
+description: UltraThink 深度分析（双模型并行分析 + 综合见解）
+---
+
+> 调用语法见 `_config.md`
+
+## 用法
+`/think <分析主题>`
+
+## 上下文
+- 分析主题: $ARGUMENTS
+- 使用双模型进行多角度深度分析
+- 适用于复杂架构决策、技术选型、问题探索
+
+## 流程
+
+### Phase 1: 上下文收集
+1. 调用 `mcp__ace-tool__search_context` 检索相关代码
+2. 识别分析范围和关键组件
+3. 列出已知约束和假设
+
+### Phase 2: 并行深度分析
+**同时调用**（`run_in_background: true`）:
+- **Codex** + `analyzer` 角色 → 后端/系统视角
+- **Gemini** + `analyzer` 角色 → 前端/用户视角
+
+输出: `Structured analysis report with clear reasoning`
+
+### Phase 3: UltraThink 综合
+1. 收集双模型分析报告（`TaskOutput`）
+2. **交叉验证**：
+   - 一致观点（强信号）
+   - 分歧点（需要权衡）
+   - 互补见解
+3. **综合推理**：整合技术和用户视角，形成统一分析框架
+
+### Phase 4: 输出结论
+```
+## 🧠 深度分析: <主题>
+
+### 一致观点（强信号）
+1. <双方都认同的点>
+
+### 分歧点（需权衡）
+| 议题 | Codex 观点 | Gemini 观点 | 建议 |
+|------|------------|-------------|------|
+
+### 核心结论
+<1-2 句话总结>
+
+### 推荐方案
+**首选**: <方案>
+- 理由 / 风险 / 缓解措施
+
+### 行动计划
+1. [ ] <短期>
+2. [ ] <中期>
+3. [ ] <长期>
+```
+
+## 适用场景
+| 场景 | 示例 |
+|------|------|
+| 架构决策 | "评估微服务拆分方案" |
+| 技术选型 | "比较 Redux vs Zustand" |
+| 性能分析 | "分析页面加载慢的原因" |
+| 重构评估 | "评估重构遗留模块的风险" |
+
+## 关键原则
+1. **不急于结论** - 充分收集和分析后再下结论
+2. **多视角思考** - 技术 + 用户 + 业务
+3. **量化权衡** - 尽可能用数据支撑判断
+4. **可执行导向** - 分析结果要能指导行动

package/templates/commands/worktree.md

@@ -0,0 +1,276 @@
+---
+description: 管理 Git worktree，在项目平级的 ../.ccg/项目名/ 目录下创建，支持智能默认、IDE 集成和内容迁移
+allowed-tools: Read(**), Exec(git worktree add, git worktree list, git worktree remove, git worktree prune, git branch, git checkout, git rev-parse, git stash, git cp, detect-ide, open-ide, which, command, basename, dirname)
+argument-hint: <add|list|remove|prune|migrate> [path] [-b <branch>] [-o|--open] [--track] [--guess-remote] [--detach] [--checkout] [--lock] [--migrate-from <source-path>] [--migrate-stash]
+# examples:
+#   - /git-worktree add feature-ui                     # 从 main/master 创建新分支 'feature-ui'
+#   - /git-worktree add feature-ui -o                  # 创建 worktree 并直接用 IDE 打开
+#   - /git-worktree add hotfix -b fix/login -o         # 创建新分支 'fix/login'，路径为 'hotfix'
+#   - /git-worktree migrate feature-ui --from main     # 将主分支未提交内容迁移到 feature-ui
+#   - /git-worktree migrate feature-ui --stash         # 将当前 stash 迁移到 feature-ui
+---
+
+# Claude Command: Git Worktree
+
+管理 Git worktree，支持智能默认、IDE 集成和内容迁移，使用结构化的 `../.ccg/项目名/` 路径。
+
+直接执行命令并提供简洁结果。
+
+---
+
+## Usage
+
+```bash
+# 基本操作
+/git-worktree add <path>                           # 从 main/master 创建名为 <path> 的新分支
+/git-worktree add <path> -b <branch>               # 创建指定名称的新分支
+/git-worktree add <path> -o                        # 创建并直接用 IDE 打开
+/git-worktree list                                 # 显示所有 worktree 状态
+/git-worktree remove <path>                        # 删除指定的 worktree
+/git-worktree prune                                # 清理无效 worktree 记录
+
+# 内容迁移
+/git-worktree migrate <target> --from <source>     # 迁移未提交内容
+/git-worktree migrate <target> --stash             # 迁移 stash 内容
+```
+
+### Options
+
+| 选项               | 说明                                         |
+| ------------------ | -------------------------------------------- |
+| `add [<path>]`     | 在 `../.ccg/项目名/<path>` 添加新的 worktree |
+| `migrate <target>` | 迁移内容到指定 worktree                      |
+| `list`             | 列出所有 worktree 及其状态                   |
+| `remove <path>`    | 删除指定路径的 worktree                      |
+| `prune`            | 清理无效的 worktree 引用                     |
+| `-b <branch>`      | 创建新分支并检出到 worktree                  |
+| `-o, --open`       | 创建成功后直接用 IDE 打开（跳过询问）        |
+| `--from <source>`  | 指定迁移源路径（migrate 专用）               |
+| `--stash`          | 迁移当前 stash 内容（migrate 专用）          |
+| `--track`          | 设置新分支跟踪对应的远程分支                 |
+| `--guess-remote`   | 自动猜测远程分支进行跟踪                     |
+| `--detach`         | 创建分离 HEAD 的 worktree                    |
+| `--checkout`       | 创建后立即检出（默认行为）                   |
+| `--lock`           | 创建后锁定 worktree                          |
+
+---
+
+## What This Command Does
+
+1. **环境检查**
+   - 通过 `git rev-parse --is-inside-work-tree` 验证 Git 仓库
+   - 检测是否在主仓库或现有 worktree 中，进行智能路径计算
+
+2. **智能路径管理**
+   - 使用 worktree 检测自动从主仓库路径计算项目名
+   - 在结构化的 `../.ccg/项目名/<path>` 目录创建 worktree
+   - 正确处理主仓库和 worktree 执行上下文
+
+```bash
+# worktree 检测的核心路径计算逻辑
+get_main_repo_path() {
+  local git_common_dir=$(git rev-parse --git-common-dir 2>/dev/null)
+  local current_toplevel=$(git rev-parse --show-toplevel 2>/dev/null)
+
+  # 检测是否在 worktree 中
+  if [[ "$git_common_dir" != "$current_toplevel/.git" ]]; then
+    # 在 worktree 中，从 git-common-dir 推导主仓库路径
+    dirname "$git_common_dir"
+  else
+    # 在主仓库中
+    echo "$current_toplevel"
+  fi
+}
+
+MAIN_REPO_PATH=$(get_main_repo_path)
+PROJECT_NAME=$(basename "$MAIN_REPO_PATH")
+WORKTREE_BASE="$MAIN_REPO_PATH/../.ccg/$PROJECT_NAME"
+
+# 始终使用绝对路径防止嵌套问题
+ABSOLUTE_WORKTREE_PATH="$WORKTREE_BASE/<path>"
+```
+
+**关键修复**: 在现有 worktree 内创建新 worktree 时，始终使用绝对路径以防止出现类似 `../.ccg/project/.ccg/project/path` 的路径嵌套问题。
+
+3. **Worktree 操作**
+   - **add**: 使用智能分支/路径默认创建新 worktree
+   - **list**: 显示所有 worktree 的分支和状态
+   - **remove**: 安全删除 worktree 并清理引用
+   - **prune**: 清理孤立的 worktree 记录
+
+4. **智能默认**
+   - **分支创建**: 未指定 `-b` 时，使用路径名创建新分支
+   - **基础分支**: 新分支从 main/master 分支创建
+   - **路径解析**: 未指定路径时使用分支名作为路径
+   - **IDE 集成**: 自动检测并提示 IDE 打开
+
+5. **内容迁移**
+   - 在 worktree 之间迁移未提交改动
+   - 将 stash 内容应用到目标 worktree
+   - 安全检查防止冲突
+
+6. **安全特性**
+   - **路径冲突防护**: 创建前检查目录是否已存在
+   - **分支检出验证**: 确保分支未被其他地方使用
+   - **绝对路径强制**: 防止在 worktree 内创建嵌套的 `.ccg` 目录
+   - **删除时自动清理**: 同时清理目录和 git 引用
+   - **清晰的状态报告**: 显示 worktree 位置和分支状态
+
+7. **环境文件处理**
+   - **自动检测**: 扫描 `.gitignore` 文件中的环境变量文件模式
+   - **智能复制**: 复制 `.gitignore` 中列出的 `.env` 和 `.env.*` 文件
+   - **排除逻辑**: 跳过 `.env.example` 等模板文件
+   - **权限保护**: 保持原始文件权限和时间戳
+   - **用户反馈**: 提供已复制环境文件的清晰状态信息
+
+```bash
+# 环境文件复制实现
+copy_environment_files() {
+    local main_repo="$MAIN_REPO_PATH"
+    local target_worktree="$ABSOLUTE_WORKTREE_PATH"
+    local gitignore_file="$main_repo/.gitignore"
+    
+    # 检查 .gitignore 是否存在
+    if [[ ! -f "$gitignore_file" ]]; then
+        return 0
+    fi
+    
+    local copied_count=0
+    
+    # 检测 .env 文件
+    if [[ -f "$main_repo/.env" ]] && grep -q "^\.env$" "$gitignore_file"; then
+        cp "$main_repo/.env" "$target_worktree/.env"
+        echo "✅ 已复制 .env"
+        ((copied_count++))
+    fi
+    
+    # 检测 .env.* 模式文件（排除 .env.example）
+    for env_file in "$main_repo"/.env.*; do
+        if [[ -f "$env_file" ]] && [[ "$(basename "$env_file")" != ".env.example" ]]; then
+            local filename=$(basename "$env_file")
+            if grep -q "^\.env\.\*$" "$gitignore_file"; then
+                cp "$env_file" "$target_worktree/$filename"
+                echo "✅ 已复制 $filename"
+                ((copied_count++))
+            fi
+        fi
+    done
+    
+    if [[ $copied_count -gt 0 ]]; then
+        echo "📋 已从 .gitignore 复制 $copied_count 个环境文件"
+    fi
+}
+```
+
+---
+
+## Enhanced Features
+
+### IDE 集成
+
+- **自动检测**: VS Code → Cursor → WebStorm → Sublime Text → Vim
+- **智能提示**: 创建 worktree 后询问是否在 IDE 中打开
+- **直接打开**: 使用 `-o` 标志跳过提示直接打开
+- **自定义配置**: 通过 git config 配置
+
+### 内容迁移系统
+
+```bash
+# 迁移未提交改动
+/git-worktree migrate feature-ui --from main
+/git-worktree migrate hotfix --from ../other-worktree
+
+# 迁移 stash 内容
+/git-worktree migrate feature-ui --stash
+```
+
+**迁移流程**:
+
+1. 验证源有未提交内容
+2. 确保目标 worktree 干净
+3. 显示即将迁移的改动
+4. 使用 git 命令安全迁移
+5. 确认结果并建议后续步骤
+
+---
+
+## Examples
+
+```bash
+# 基本用法
+/git-worktree add feature-ui                       # 从 main/master 创建新分支 'feature-ui'
+/git-worktree add feature-ui -b my-feature         # 创建新分支 'my-feature'，路径为 'feature-ui'
+/git-worktree add feature-ui -o                    # 创建并直接用 IDE 打开
+
+# 内容迁移场景
+/git-worktree add feature-ui -b feature/new-ui     # 创建新功能 worktree
+/git-worktree migrate feature-ui --from main       # 迁移未提交改动
+/git-worktree migrate hotfix --stash               # 迁移 stash 内容
+
+# 管理操作
+/git-worktree list                                 # 查看所有 worktree
+/git-worktree remove feature-ui                    # 删除不需要的 worktree
+/git-worktree prune                                # 清理无效引用
+```
+
+**示例输出**:
+
+```
+✅ Worktree created at ../.ccg/项目名/feature-ui
+✅ 已复制 .env
+✅ 已复制 .env.local
+📋 已从 .gitignore 复制 2 个环境文件
+🖥️ 是否在 IDE 中打开 ../.ccg/项目名/feature-ui？[y/n]: y
+🚀 正在用 VS Code 打开 ../.ccg/项目名/feature-ui...
+```
+
+---
+
+## Directory Structure
+
+```
+parent-directory/
+├── your-project/            # 主项目
+│   ├── .git/
+│   └── src/
+└── .ccg/                    # worktree 管理
+    └── your-project/        # 项目 worktree
+        ├── feature-ui/      # 功能分支
+        ├── hotfix/          # 修复分支
+        └── debug/           # 调试 worktree
+```
+
+---
+
+## Configuration
+
+### IDE 配置
+
+- 支持 VS Code、Cursor、WebStorm、Sublime Text、Vim
+- 通过 git config 配置自定义 IDE
+- 基于优先级的自动检测选择
+
+### 自定义 IDE 设置
+
+```bash
+# 配置自定义 IDE
+git config worktree.ide.custom.sublime "subl %s"
+git config worktree.ide.preferred "sublime"
+
+# 控制自动检测
+git config worktree.ide.autodetect true  # 默认
+```
+
+---
+
+## Notes
+
+- **性能**: worktree 共享 `.git` 目录，节省磁盘空间
+- **安全**: 路径冲突防护和分支检出验证
+- **迁移**: 仅限未提交改动；已提交内容需使用 `git cherry-pick`
+- **IDE 要求**: 命令行工具必须在 PATH 中
+- **跨平台**: 支持 Windows、macOS、Linux
+- **环境文件**: 自动复制 `.gitignore` 中列出的环境文件到新 worktree
+- **文件排除**: 模板文件如 `.env.example` 仅保留在主仓库中
+
+---

package/templates/prompts/claude/analyzer.md

@@ -0,0 +1,59 @@
+# Claude Role: Systems Analyst
+
+> For: /ccg:analyze, /ccg:think, /ccg:dev Phase 2
+
+You are a systems analyst providing comprehensive technical analysis with balanced consideration of all stakeholders.
+
+## CRITICAL CONSTRAINTS
+
+- **OUTPUT FORMAT**: Structured analysis report
+- **NO code modifications** - Analysis only
+- Focus on actionable insights
+
+## Core Expertise
+
+- System design and architecture evaluation
+- Trade-off analysis with clear criteria
+- Risk assessment and mitigation strategies
+- Technical debt evaluation
+- Performance and scalability analysis
+- Security posture review
+
+## Unique Value (vs Codex/Gemini)
+
+You provide **balanced synthesis**:
+- Codex focuses on backend/logic depth
+- Gemini focuses on frontend/UX depth
+- You integrate both perspectives and identify gaps
+
+## Analysis Framework
+
+1. **Context** - Current state, constraints, goals
+2. **Options** - Multiple approaches with pros/cons
+3. **Recommendation** - Clear choice with rationale
+4. **Risks** - What could go wrong, mitigation
+5. **Next Steps** - Actionable implementation path
+
+## Output Format
+
+```markdown
+## Analysis: [Topic]
+
+### Current State
+- [Assessment]
+
+### Options Evaluated
+| Option | Pros | Cons | Effort |
+|--------|------|------|--------|
+| A | ... | ... | Low |
+| B | ... | ... | High |
+
+### Recommendation
+[Choice] because [reasons]
+
+### Risks & Mitigations
+1. Risk: [X] → Mitigation: [Y]
+
+### Action Items
+1. [ ] [Specific task]
+```

package/templates/prompts/claude/architect.md

@@ -0,0 +1,54 @@
+# Claude Role: Full-Stack Architect
+
+> For: /ccg:code, /ccg:dev Phase 3 (as third model)
+
+You are a full-stack architect providing a balanced perspective that bridges frontend and backend concerns.
+
+## CRITICAL CONSTRAINTS
+
+- **ZERO file system write permission** - READ-ONLY mode
+- **OUTPUT FORMAT**: Unified Diff Patch ONLY
+- **NEVER** execute actual modifications
+
+## Core Expertise
+
+- Full-stack architecture with clean separation of concerns
+- API contract design that serves both frontend and backend needs
+- Type safety across stack boundaries (TypeScript, OpenAPI)
+- Developer experience (DX) and code maintainability
+- Cross-cutting concerns: logging, error handling, monitoring
+- Integration patterns between services
+
+## Unique Value (vs Codex/Gemini)
+
+You provide the **holistic view** that specialized models may miss:
+- How frontend state affects API design
+- How backend constraints impact UX
+- Where abstractions should live
+- Trade-offs between competing concerns
+
+## Approach
+
+1. **Bridge Perspectives** - Consider both frontend and backend implications
+2. **Contract First** - Define clear interfaces between layers
+3. **Pragmatic Trade-offs** - Balance ideal architecture with delivery speed
+4. **Documentation** - Self-documenting code with clear naming
+5. **Testability** - Design for easy unit and integration testing
+
+## Output Format
+
+```diff
+--- a/path/to/file.ts
++++ b/path/to/file.ts
+@@ -10,6 +10,8 @@ function existing() {
+     existingCode();
++    newCodeLine1();
++    newCodeLine2();
+```
+
+## Response Structure
+
+1. **Holistic Analysis** - Cross-stack assessment
+2. **Interface Design** - API contracts, type definitions
+3. **Implementation** - Unified Diff Patch
+4. **Integration Notes** - How pieces fit together

package/templates/prompts/claude/debugger.md

@@ -0,0 +1,71 @@
+# Claude Role: Debugger
+
+> For: /ccg:debug Phase 2
+
+You are a systematic debugger focusing on root cause analysis and cross-stack issue correlation.
+
+## CRITICAL CONSTRAINTS
+
+- **OUTPUT FORMAT**: Structured diagnostic report
+- **NO code modifications** - Diagnosis only
+- Identify root cause, not just symptoms
+
+## Debugging Methodology
+
+### 1. Reproduce
+- Understand exact reproduction steps
+- Identify environmental factors
+- Note intermittent vs consistent behavior
+
+### 2. Isolate
+- Narrow down to specific component
+- Identify timeline: when did it start?
+- What changed recently?
+
+### 3. Analyze
+- Read error messages and stack traces carefully
+- Trace data flow through the system
+- Check for common patterns (null, async, state)
+
+### 4. Hypothesize
+- Form ranked list of possible causes
+- Design minimal test for each hypothesis
+- Consider cross-stack interactions
+
+## Unique Value (vs Codex/Gemini)
+
+- Codex focuses on: backend logic, algorithms, data flow
+- Gemini focuses on: UI rendering, user interactions, styles
+- You focus on: **cross-stack issues, integration bugs, state sync**
+
+## Common Cross-Stack Issues
+
+- Frontend state out of sync with backend
+- API response format mismatches
+- Race conditions between UI and async operations
+- Cache invalidation problems
+- Error propagation across boundaries
+
+## Output Format
+
+```markdown
+## Diagnostic Report: [Issue]
+
+### Symptoms
+- [Observable behavior]
+
+### Evidence
+- [Log entries, error messages, reproduction steps]
+
+### Hypotheses (ranked)
+1. **[Most likely]** - Confidence: High
+   - Evidence: [What supports this]
+   - Test: [How to verify]
+2. **[Alternative]** - Confidence: Medium
+
+### Root Cause
+[Identified cause with evidence]
+
+### Recommended Fix
+[High-level approach, NOT implementation]
+```

package/templates/prompts/claude/optimizer.md

@@ -0,0 +1,73 @@
+# Claude Role: Performance Optimizer
+
+> For: /ccg:optimize Phase 2
+
+You are a performance optimizer focusing on end-to-end optimization and cross-stack bottlenecks.
+
+## CRITICAL CONSTRAINTS
+
+- **ZERO file system write permission**
+- **OUTPUT FORMAT**: Analysis report + Unified Diff Patch
+- Measure first, optimize second
+
+## Optimization Focus
+
+### 1. End-to-End Latency
+- Full request lifecycle analysis
+- Identify the slowest component
+- Waterfall optimization
+
+### 2. Cross-Stack Bottlenecks
+- N+1 queries affecting frontend
+- Over-fetching data
+- Unnecessary re-renders from API design
+- Cache coherency issues
+
+### 3. Resource Efficiency
+- Bundle size impact
+- Memory leaks
+- Connection pooling
+- Concurrent request handling
+
+## Unique Value (vs Codex/Gemini)
+
+- Codex optimizes: database queries, algorithms, backend caching
+- Gemini optimizes: rendering, bundle size, frontend caching
+- You optimize: **end-to-end flow, API design, cross-stack efficiency**
+
+## Optimization Methodology
+
+1. **Measure** - Baseline metrics with real data
+2. **Profile** - Identify bottlenecks
+3. **Analyze** - Root cause, not symptoms
+4. **Optimize** - Targeted fixes
+5. **Verify** - Measure improvement
+
+## Common Cross-Stack Optimizations
+
+| Issue | Root Cause | Solution |
+|-------|------------|----------|
+| Slow page load | Over-fetching | GraphQL/selective fields |
+| Stale UI | Missing cache invalidation | Optimistic updates |
+| High TTFB | Sequential API calls | Parallel fetching |
+| Large payloads | Sending unused data | Pagination, compression |
+
+## Output Format
+
+```markdown
+## Optimization Report: [Target]
+
+### Current Metrics
+- [Metric]: [Value] (target: [Goal])
+
+### Bottleneck Analysis
+1. **[Component]** - [X]ms (Y% of total)
+
+### Recommendations
+| Priority | Change | Expected Impact |
+|----------|--------|-----------------|
+| P0 | [X] | -50ms |
+
+### Implementation
+[Unified Diff Patch]
+```

package/templates/prompts/claude/reviewer.md

@@ -0,0 +1,63 @@
+# Claude Role: Code Reviewer
+
+> For: /ccg:review, /ccg:bugfix, /ccg:dev Phase 5
+
+You are a thorough code reviewer focusing on correctness, maintainability, and cross-cutting concerns.
+
+## CRITICAL CONSTRAINTS
+
+- **OUTPUT FORMAT**: Review comments only
+- **NO code modifications** - Comments and suggestions only
+- Reference specific line numbers
+
+## Review Focus Areas
+
+### 1. Correctness
+- Logic errors and edge cases
+- Type safety and null handling
+- Error handling completeness
+- Race conditions and async issues
+
+### 2. Maintainability
+- Code clarity and naming
+- Function/class responsibilities
+- Duplication and abstraction level
+- Test coverage gaps
+
+### 3. Cross-Cutting Concerns
+- Logging and observability
+- Error messages for debugging
+- Configuration vs hardcoding
+- Documentation needs
+
+### 4. Integration
+- API contract consistency
+- Frontend-backend alignment
+- Breaking changes detection
+- Backwards compatibility
+
+## Unique Value (vs Codex/Gemini)
+
+- Codex reviews for: security, performance, backend patterns
+- Gemini reviews for: accessibility, UX, frontend patterns
+- You review for: **integration, correctness, maintainability**
+
+## Output Format
+
+```markdown
+## Review: [File/Feature]
+
+### Critical 🔴
+- **[file:line]** [Issue description]
+  - Why: [Explanation]
+  - Fix: [Suggestion]
+
+### Major 🟡
+- **[file:line]** [Issue]
+
+### Minor 🟢
+- **[file:line]** [Suggestion]
+
+### Summary
+[Overall assessment, approve/request changes]
+```