ccg-workflow 1.7.79 → 1.7.81

package/README.md

@@ -17,7 +17,7 @@ A multi-model collaboration development system where Claude Code orchestrates Co
 
 - **Zero-config model routing** — Frontend tasks automatically go to Gemini, backend tasks to Codex. No manual switching.
 - **Security by design** — External models have no write access. They return patches; Claude reviews before applying.
-- **26 slash commands** — From planning to execution, git workflow to code review, all accessible via `/ccg:*`.
+- **27 slash commands** — From planning to execution, git workflow to code review, all accessible via `/ccg:*`.
 - **Spec-driven development** — Integrates [OPSX](https://github.com/fission-ai/opsx) to turn vague requirements into verifiable constraints, eliminating AI improvisation.
 
 ## Architecture
@@ -141,6 +141,7 @@ Supports: npm, homebrew, curl, powershell, cmd.
 | Command | Description |
 |---------|-------------|
 | `/ccg:init` | Initialize project CLAUDE.md |
+| `/ccg:context` | Project context management (.context/ init, log, compress, history) |
 
 ## Workflow Guides
 
@@ -352,4 +353,4 @@ MIT
 
 ---
 
-v1.7.79 | [Issues](https://github.com/fengshao1227/ccg-workflow/issues) | [Contributing](./CONTRIBUTING.md)
+v1.7.81 | [Issues](https://github.com/fengshao1227/ccg-workflow/issues) | [Contributing](./CONTRIBUTING.md)

package/README.zh-CN.md

@@ -17,7 +17,7 @@ Claude Code 编排 Codex + Gemini 的多模型协作开发系统。前端任务
 
 - **零配置模型路由** — 前端任务自动走 Gemini，后端任务自动走 Codex，无需手动切换。
 - **安全设计** — 外部模型无写入权限，仅返回 Patch，由 Claude 审核后应用。
-- **26 个斜杠命令** — 从规划到执行、Git 工作流到代码审查，通过 `/ccg:*` 一站式访问。
+- **27 个斜杠命令** — 从规划到执行、Git 工作流到代码审查，通过 `/ccg:*` 一站式访问。
 - **规范驱动开发** — 集成 [OPSX](https://github.com/fission-ai/opsx)，将模糊需求变成可验证约束，让 AI 没法自由发挥。
 
 ## 架构
@@ -141,6 +141,7 @@ npx ccg-workflow menu  # 选择「安装 Claude Code」
 | 命令 | 说明 |
 |------|------|
 | `/ccg:init` | 初始化项目 CLAUDE.md |
+| `/ccg:context` | 项目上下文管理（.context 初始化/日志/压缩/历史） |
 
 ## 工作流指南
 
@@ -196,7 +197,7 @@ npx ccg-workflow menu  # 选择「安装 Claude Code」
 
 ```
 ~/.claude/
-├── commands/ccg/       # 26 个斜杠命令
+├── commands/ccg/       # 27 个斜杠命令
 ├── agents/ccg/         # 子智能体
 ├── skills/ccg/         # 质量关卡 + 多 Agent 协同
 ├── bin/codeagent-wrapper
@@ -352,4 +353,4 @@ MIT
 
 ---
 
-v1.7.79 | [Issues](https://github.com/fengshao1227/ccg-workflow/issues) | [参与贡献](./CONTRIBUTING.md)
+v1.7.81 | [Issues](https://github.com/fengshao1227/ccg-workflow/issues) | [参与贡献](./CONTRIBUTING.md)

package/dist/cli.mjs

@@ -1,7 +1,7 @@
 #!/usr/bin/env node
 import cac from 'cac';
 import ansis from 'ansis';
-import { z as diagnoseMcpConfig, A as isWindows, B as readClaudeCodeConfig, C as fixWindowsMcpConfig, D as writeClaudeCodeConfig, r as readCcgConfig, b as initI18n, a as i18n, s as showMainMenu, i as init, E as configMcp, F as version } from './shared/ccg-workflow.O8zwMZ2s.mjs';
+import { z as diagnoseMcpConfig, A as isWindows, B as readClaudeCodeConfig, C as fixWindowsMcpConfig, D as writeClaudeCodeConfig, r as readCcgConfig, b as initI18n, a as i18n, s as showMainMenu, i as init, E as configMcp, F as version } from './shared/ccg-workflow.DLkUGirT.mjs';
 import 'inquirer';
 import 'node:child_process';
 import 'node:util';

package/dist/index.d.mts

@@ -83,6 +83,7 @@ interface InstallResult {
     installedCommands: string[];
     installedPrompts: string[];
     installedSkills?: number;
+    installedRules?: boolean;
     errors: string[];
     configPath: string;
     binPath?: string;
@@ -149,6 +150,7 @@ interface UninstallResult {
     removedPrompts: string[];
     removedAgents: string[];
     removedSkills: string[];
+    removedRules: boolean;
     removedBin: boolean;
     errors: string[];
 }

package/dist/index.d.ts

@@ -83,6 +83,7 @@ interface InstallResult {
     installedCommands: string[];
     installedPrompts: string[];
     installedSkills?: number;
+    installedRules?: boolean;
     errors: string[];
     configPath: string;
     binPath?: string;
@@ -149,6 +150,7 @@ interface UninstallResult {
     removedPrompts: string[];
     removedAgents: string[];
     removedSkills: string[];
+    removedRules: boolean;
     removedBin: boolean;
     errors: string[];
 }

package/dist/index.mjs

@@ -1,4 +1,4 @@
-export { c as changeLanguage, x as checkForUpdates, y as compareVersions, d as createDefaultConfig, e as createDefaultRouting, g as getCcgDir, f as getConfigPath, t as getCurrentVersion, v as getLatestVersion, j as getWorkflowById, h as getWorkflowConfigs, a as i18n, i as init, b as initI18n, l as installAceTool, m as installAceToolRs, k as installWorkflows, p as migrateToV1_4_0, q as needsMigration, r as readCcgConfig, s as showMainMenu, o as uninstallAceTool, n as uninstallWorkflows, u as update, w as writeCcgConfig } from './shared/ccg-workflow.O8zwMZ2s.mjs';
+export { c as changeLanguage, x as checkForUpdates, y as compareVersions, d as createDefaultConfig, e as createDefaultRouting, g as getCcgDir, f as getConfigPath, t as getCurrentVersion, v as getLatestVersion, j as getWorkflowById, h as getWorkflowConfigs, a as i18n, i as init, b as initI18n, l as installAceTool, m as installAceToolRs, k as installWorkflows, p as migrateToV1_4_0, q as needsMigration, r as readCcgConfig, s as showMainMenu, o as uninstallAceTool, n as uninstallWorkflows, u as update, w as writeCcgConfig } from './shared/ccg-workflow.DLkUGirT.mjs';
 import 'ansis';
 import 'inquirer';
 import 'node:child_process';

package/dist/shared/{ccg-workflow.O8zwMZ2s.mjs → ccg-workflow.DLkUGirT.mjs}

@@ -10,7 +10,7 @@ import { parse, stringify } from 'smol-toml';
 import i18next from 'i18next';
 import ora from 'ora';
 
-const version = "1.7.79";
+const version = "1.7.81";
 
 function isWindows() {
   return process.platform === "win32";
@@ -503,6 +503,17 @@ const WORKFLOW_CONFIGS = [
     order: 3,
     description: "\u8BFB\u53D6 /ccg:plan \u8BA1\u5212\u6587\u4EF6\uFF0CCodex \u5168\u6743\u6267\u884C + \u591A\u6A21\u578B\u5BA1\u6838",
     descriptionEn: "Read plan file from /ccg:plan, Codex executes + multi-model review"
+  },
+  {
+    id: "context",
+    name: "\u9879\u76EE\u4E0A\u4E0B\u6587\u7BA1\u7406",
+    nameEn: "Project Context Manager",
+    category: "development",
+    commands: ["context"],
+    defaultSelected: true,
+    order: 4,
+    description: "\u521D\u59CB\u5316 .context \u76EE\u5F55\u3001\u8BB0\u5F55\u51B3\u7B56\u65E5\u5FD7\u3001\u538B\u7F29\u5F52\u6863\u3001\u67E5\u770B\u5386\u53F2",
+    descriptionEn: "Init .context dir, log decisions, compress, view history"
   }
 ];
 function getWorkflowConfigs() {
@@ -748,6 +759,28 @@ ${workflow.description}
       result.success = false;
     }
   }
+  const rulesTemplateDir = join(templateDir, "rules");
+  const rulesDestDir = join(installDir, "rules");
+  if (await fs.pathExists(rulesTemplateDir)) {
+    try {
+      await fs.ensureDir(rulesDestDir);
+      const rulesFiles = await fs.readdir(rulesTemplateDir);
+      for (const file of rulesFiles) {
+        if (file.endsWith(".md")) {
+          const srcFile = join(rulesTemplateDir, file);
+          const destFile = join(rulesDestDir, file);
+          if (force || !await fs.pathExists(destFile)) {
+            const templateContent = await fs.readFile(srcFile, "utf-8");
+            const processedContent = replaceHomePathsInTemplate(templateContent, installDir);
+            await fs.writeFile(destFile, processedContent, "utf-8");
+          }
+        }
+      }
+      result.installedRules = true;
+    } catch (error) {
+      result.errors.push(`Failed to install rules: ${error}`);
+    }
+  }
   try {
     const binDir = join(installDir, "bin");
     await fs.ensureDir(binDir);
@@ -793,6 +826,7 @@ async function uninstallWorkflows(installDir) {
     removedPrompts: [],
     removedAgents: [],
     removedSkills: [],
+    removedRules: false,
     removedBin: false,
     errors: []
   };
@@ -800,6 +834,7 @@ async function uninstallWorkflows(installDir) {
   join(installDir, ".ccg", "prompts");
   const agentsDir = join(installDir, "agents", "ccg");
   const skillsDir = join(installDir, "skills", "ccg");
+  const rulesDir = join(installDir, "rules");
   const binDir = join(installDir, "bin");
   const ccgConfigDir = join(installDir, ".ccg");
   if (await fs.pathExists(commandsDir)) {
@@ -850,6 +885,20 @@ async function uninstallWorkflows(installDir) {
       result.success = false;
     }
   }
+  if (await fs.pathExists(rulesDir)) {
+    try {
+      const ccgRuleFiles = ["ccg-skills.md", "ccg-grok-search.md"];
+      for (const ruleFile of ccgRuleFiles) {
+        const rulePath = join(rulesDir, ruleFile);
+        if (await fs.pathExists(rulePath)) {
+          await fs.remove(rulePath);
+          result.removedRules = true;
+        }
+      }
+    } catch (error) {
+      result.errors.push(`Failed to remove rules: ${error}`);
+    }
+  }
   if (await fs.pathExists(binDir)) {
     try {
       const wrapperName = process.platform === "win32" ? "codeagent-wrapper.exe" : "codeagent-wrapper";
@@ -3121,6 +3170,12 @@ async function init(options = {}) {
       console.log(`    ${ansis.green("\u2713")} ${result.installedSkills} skills installed (quality gates + multi-agent)`);
       console.log(ansis.gray("       \u2192 ~/.claude/skills/"));
     }
+    if (result.installedRules) {
+      console.log();
+      console.log(ansis.cyan("  Rules:"));
+      console.log(`    ${ansis.green("\u2713")} quality gate auto-trigger rules`);
+      console.log(ansis.gray("       \u2192 ~/.claude/rules/ccg-skills.md"));
+    }
     if (result.errors.length > 0) {
       console.log();
       console.log(ansis.red(`  \u26A0 ${i18n.t("init:installationErrors")}`));

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ccg-workflow",
-  "version": "1.7.79",
+  "version": "1.7.81",
   "description": "Claude + Codex + Gemini multi-model collaboration system - smart routing development workflow",
   "type": "module",
   "packageManager": "pnpm@10.17.1",
@@ -54,6 +54,7 @@
     "templates/commands/team-exec.md",
     "templates/commands/team-review.md",
     "templates/commands/codex-exec.md",
+    "templates/commands/context.md",
     "templates/commands/agents/",
     "templates/prompts/codex/",
     "templates/prompts/gemini/analyzer.md",
@@ -65,7 +66,8 @@
     "templates/prompts/gemini/tester.md",
     "templates/prompts/claude/",
     "templates/output-styles/",
-    "templates/skills/"
+    "templates/skills/",
+    "templates/rules/"
   ],
   "scripts": {
     "dev": "tsx src/cli.ts",

package/templates/commands/commit.md

@@ -68,7 +68,36 @@ description: '智能 Git 提交：分析改动生成 Conventional Commit 信息
 
 **语言**：根据最近 50 次提交判断中文/英文
 
-### ✅ 阶段 5：执行提交
+### 📦 阶段 5：Context 自动归档（若 .context/ 存在）
+
+`[模式：上下文归档]`
+
+**前置判断**：
+- 若 `.context/` 目录不存在 → 在提交成功后输出提示：`💡 建议执行 /ccg:context init 启用决策追踪`，不阻断
+- 若 `.context/` 存在 → 执行以下步骤
+
+**从 git diff 自动生成 ContextEntry**：
+
+1. 获取当前分支名：`git branch --show-current`
+2. 获取暂存区变更：`git diff --cached --stat` + `git diff --cached`（完整 diff）
+3. **分析 diff 生成 ContextEntry**：
+   - `summary`：从阶段 4 生成的 commit message 中取首行
+   - `decisions`：分析 diff 中的关键变更（新增依赖、架构调整、接口变更、配置修改），推断决策理由
+   - `bugs`：若 commit type 为 `fix`，从 diff 中提取 bug 症状、根因、修复方式
+   - `changes.files`：从 `git diff --cached --name-only` 提取
+   - `tests`：若变更包含测试文件，记录测试相关信息
+4. **合并 session.log**（可选）：若 `.context/current/branches/<branch>/session.log` 存在且非空，将其中的手动记录合并到 decisions/bugs 中，然后清空 session.log
+5. **脱敏**：扫描 token/key/password/secret 模式 → 替换为 `[REDACTED]`
+6. **追加**：将 ContextEntry 作为一行追加到 `.context/history/commits.jsonl`
+7. **重生成**：更新 `.context/history/commits.md` 人类视图
+8. **暂存**：`git add .context/history/`
+9. **Trailer**：在 commit message 中添加 `Context-Id: <uuid>` trailer
+
+**ContextEntry 格式**参见 `/ccg:context` 命令中的 Schema 定义。
+
+**失败降级**：若归档过程出错，不阻断提交。写入 minimal ContextEntry（仅 summary + files），继续正常提交。
+
+### ✅ 阶段 6：执行提交
 
 `[模式：执行]`
 

package/templates/commands/context.md

@@ -0,0 +1,332 @@
+---
+description: '项目上下文管理：初始化 .context 目录、记录决策日志、压缩归档、查看历史'
+---
+
+# Context - 项目上下文管理
+
+管理 `.context/` 目录结构，为 LLM 工具提供决策审计链。
+
+## 使用方法
+
+```bash
+/context <subcommand> [options]
+```
+
+## 子命令
+
+| 子命令 | 说明 |
+|--------|------|
+| `init` | 初始化 `.context/` 目录结构 |
+| `log <message>` | （可选）手动追加备注到 session.log，commit 时会合并 |
+| `show` | 查看当前分支的 session.log |
+| `compress` | 压缩 session.log → uncommit.md（手动预览用） |
+| `history` | 查看 history/commits.md |
+| `squash <ids...>` | 合并多条 history 记录（配合 git squash） |
+
+> **核心用法**：`init` 一次，之后只管开发。`/ccg:commit` 提交时自动从 git diff 分析决策并归档到 history/。`log` 仅在你想手动补充备注时使用。
+
+---
+
+## 执行工作流
+
+### 子命令：init
+
+`[模式：初始化]`
+
+在当前项目根目录创建 `.context/` 结构：
+
+1. 检测项目根目录（查找 `.git/`）
+2. 若 `.context/` 已存在，跳过已有文件，仅补全缺失
+3. 创建以下结构：
+
+```
+.context/
+├── .gitignore
+├── .gitattributes
+├── prefs/
+│   ├── coding-style.md
+│   └── workflow.md
+├── current/
+│   └── branches/
+│       └── .gitkeep
+└── history/
+    ├── commits.jsonl
+    ├── commits.md
+    └── archives/
+        └── .gitkeep
+```
+
+4. **创建 `.context/.gitignore`**：
+
+```gitignore
+# Ephemeral workspace — never commit
+current/
+
+# Raw interaction logs — always local only
+**/session.log
+**/session.raw.log
+**/*.session.log
+**/*.raw.log
+
+# Editor / temp
+**/*.tmp
+**/*.bak
+**/*.swp
+```
+
+5. **创建 `.context/.gitattributes`**：
+
+```
+# JSONL append-only: 'union' merge reduces conflicts
+history/commits.jsonl merge=union
+history/archives/*.jsonl merge=union
+```
+
+6. **创建 `.context/prefs/coding-style.md`**（团队编码规范模板）：
+
+```markdown
+# Coding Style Guide
+
+> 此文件定义团队编码规范，所有 LLM 工具在修改代码时必须遵守。
+> 提交到 Git，团队共享。
+
+## General
+- Prefer small, reviewable changes; avoid unrelated refactors.
+- Keep functions short (<50 lines); avoid deep nesting (≤3 levels).
+- Name things explicitly; no single-letter variables except loop counters.
+- Handle errors explicitly; never swallow errors silently.
+
+## Language-Specific
+<!-- 根据项目语言补充，例如：-->
+<!-- ### TypeScript -->
+<!-- - Use strict mode; prefer `interface` over `type` for object shapes. -->
+
+## Git Commits
+- Conventional Commits, imperative mood.
+- Atomic commits: one logical change per commit.
+
+## Testing
+- Every feat/fix MUST include corresponding tests.
+- Coverage must not decrease.
+- Fix flow: write failing test FIRST, then fix code.
+
+## Security
+- Never log secrets (tokens/keys/cookies/JWT).
+- Validate inputs at trust boundaries.
+```
+
+7. **创建 `.context/prefs/workflow.md`**（LLM 工作流规则）：
+
+```markdown
+# Development Workflow Rules
+
+> 此文件定义 LLM 开发工作流的强制规则。
+> 所有 LLM 工具在执行任务时必须遵守，不可跳过任何步骤。
+
+## Full Flow (MUST follow, no exceptions)
+
+### feat (新功能)
+1. 理解需求，分析影响范围
+2. 读取现有代码，理解模式
+3. 编写实现代码
+4. 编写对应测试
+5. 运行测试，修复失败
+6. 更新文档（若 API 变更）
+7. 自查 lint / type-check
+
+### fix (缺陷修复)
+1. 复现问题，确认症状
+2. 定位根因
+3. 编写失败测试（先有红灯）
+4. 修复代码
+5. 验证测试通过（变绿灯）
+6. 回归测试
+
+### refactor (重构)
+1. 确保现有测试通过
+2. 小步重构，每步可验证
+3. 重构后测试必须全部通过
+4. 不改变外部行为
+
+## Context Logging (决策记录)
+
+当你做出以下决策时，MUST 追加到 `.context/current/branches/<当前分支>/session.log`：
+
+1. **方案选择**：选 A 不选 B 时，记录原因
+2. **Bug 发现与修复**：根因 + 修复方法 + 教训
+3. **API/架构决策**：接口设计选择
+4. **放弃的方案**：为什么放弃
+
+追加格式：
+
+## <ISO-8601 时间>
+**Decision**: <你选择了什么>
+**Alternatives**: <被排除的方案>
+**Reason**: <为什么>
+**Risk**: <潜在风险>
+```
+
+8. **创建 `.context/history/commits.jsonl`**（空文件）
+
+9. **创建 `.context/history/commits.md`**（人类视图模板）：
+
+```markdown
+# Commit Decision History
+
+> 此文件是 `commits.jsonl` 的人类可读视图，可由工具重生成。
+> Canonical store: `commits.jsonl` (JSONL, append-only)
+
+| Date | Context-Id | Commit | Summary | Decisions | Bugs | Risk |
+|------|-----------|--------|---------|-----------|------|------|
+```
+
+10. **注入 CLAUDE.md 引用**（若项目存在 CLAUDE.md）：
+
+检测项目根目录是否有 `CLAUDE.md`，若有则在末尾追加：
+
+```markdown
+
+## .context 项目上下文
+
+> 项目使用 `.context/` 管理开发决策上下文。
+
+- 编码规范：`.context/prefs/coding-style.md`
+- 工作流规则：`.context/prefs/workflow.md`
+- 决策历史：`.context/history/commits.md`
+
+**规则**：修改代码前必读 prefs/，做决策时按 workflow.md 规则记录日志。
+```
+
+11. 输出初始化结果摘要
+
+---
+
+### 子命令：log
+
+`[模式：记录]`
+
+1. 获取当前 Git 分支名：`git branch --show-current`
+2. 确保 `.context/current/branches/<branch>/` 目录存在
+3. 将 `<message>` 以结构化格式追加到 `session.log`：
+
+```markdown
+## <ISO-8601 当前时间>
+<message>
+```
+
+---
+
+### 子命令：show
+
+`[模式：查看]`
+
+1. 获取当前分支名
+2. 读取 `.context/current/branches/<branch>/session.log`
+3. 若不存在，提示 "当前分支暂无决策日志"
+4. 输出内容
+
+---
+
+### 子命令：compress
+
+`[模式：压缩]`
+
+将 `session.log` 压缩为结构化 `uncommit.md`，供提交前审查。
+
+1. 读取 `.context/current/branches/<branch>/session.log`
+2. 若为空，提示无内容可压缩
+3. **脱敏**：扫描并替换潜在敏感信息（token/key/password → `[REDACTED]`）
+4. **结构化提取**：从日志中提取 decisions / bugs / alternatives
+5. **生成 uncommit.md**：
+
+```markdown
+# Pre-commit Summary: <branch-name>
+
+| Time | Summary | Decision | Method | Result & Bug |
+|------|---------|----------|--------|--------------|
+| ... | ... | ... | ... | ... |
+```
+
+6. 输出压缩结果供用户审查
+7. 提示用户：确认后可执行 `/ccg:commit` 提交
+
+---
+
+### 子命令：history
+
+`[模式：查看]`
+
+1. 读取 `.context/history/commits.md`
+2. 若不存在，提示 "暂无历史记录，请先使用 /ccg:context init"
+3. 输出内容
+4. 若用户指定文件路径，从 `commits.jsonl` 检索 `changes.files` 包含该路径的条目
+
+---
+
+### 子命令：squash
+
+`[模式：合并]`
+
+配合 `git squash` 使用，合并多条 ContextEntry。
+
+1. 接收 Context-Id 列表
+2. 从 `commits.jsonl` 读取对应条目
+3. 生成新的聚合 ContextEntry：
+   - 新 `context_id`（UUIDv7）
+   - `Context-Refs` = 所有被 squash 的 ids
+   - 合并 decisions / bugs / changes
+4. 追加到 `commits.jsonl`
+5. 重生成 `commits.md`
+
+---
+
+## ContextEntry Schema (v1.0.0)
+
+每条 JSONL 记录格式：
+
+```json
+{
+  "schema_version": "1.0.0",
+  "context_id": "<UUIDv7>",
+  "created_at": "<ISO-8601>",
+  "producer": {
+    "tool": "<tool-name>",
+    "llm": { "provider": "<provider>", "model": "<model>" }
+  },
+  "git": {
+    "branch": "<branch>",
+    "commit_sha": "<short-sha>",
+    "trailers": { "Context-Id": "<uuid>" }
+  },
+  "summary": "<one-line summary>",
+  "decisions": [{
+    "title": "<decision title>",
+    "rationale": "<why>",
+    "tradeoffs": ["<tradeoff>"],
+    "assumptions": ["<assumption>"],
+    "rejected_alternatives": [{ "option": "<alt>", "reason": "<why rejected>" }],
+    "side_effects": ["<side effect>"]
+  }],
+  "bugs": [{
+    "symptom": "<what happened>",
+    "root_cause": "<why>",
+    "fix": "<how fixed>",
+    "lesson": "<takeaway>"
+  }],
+  "changes": { "files": ["<path>"] },
+  "tests": [{ "command": "<cmd>", "result": "<pass/fail>", "coverage": "<pct>" }],
+  "privacy": { "classification": "internal", "redactions_applied": true }
+}
+```
+
+---
+
+## 关键规则
+
+1. **prefs/ 提交到 Git** — 团队共享编码规范
+2. **current/ 永不提交** — 原始日志仅本地
+3. **history/ 提交到 Git** — 永久决策归档
+4. **commits.jsonl 是 canonical** — commits.md 可重生成
+5. **UUIDv7 为主键** — 不依赖 commit SHA（rebase-safe）
+6. **merge=union** — JSONL append 冲突自动合并
+7. **脱敏先于一切** — 任何写入 history 前必须脱敏

package/templates/prompts/codex/analyzer.md

@@ -48,3 +48,11 @@ You are a senior technical analyst specializing in architecture evaluation, solu
 3. **Options** - Alternative approaches with pros/cons
 4. **Recommendation** - Preferred approach with rationale
 5. **Action Items** - Concrete next steps
+
+## .context Awareness
+
+If the project has a `.context/` directory:
+1. Read `.context/prefs/coding-style.md` and `.context/prefs/workflow.md` before analysis
+2. Use rules from prefs/ as evaluation criteria
+3. When analyzing, check `.context/history/commits.jsonl` for related past decisions
+4. Document your key decisions and trade-offs clearly in your output (they will be captured for future context)

package/templates/prompts/codex/architect.md

@@ -44,3 +44,11 @@ You are a senior backend architect specializing in scalable API design, database
 2. **Architecture Decision** - Key design choices with rationale
 3. **Implementation** - Unified Diff Patch
 4. **Considerations** - Performance, security, scaling notes
+
+## .context Awareness
+
+If the project has a `.context/` directory:
+1. Read `.context/prefs/coding-style.md` and `.context/prefs/workflow.md` before designing
+2. Follow all coding conventions defined in prefs/
+3. Check `.context/history/commits.jsonl` for past architectural decisions on related modules
+4. In your Architecture Decision section, clearly state: rationale, rejected alternatives, assumptions, and potential side effects (these will be captured as ContextEntry for future reference)

package/templates/prompts/codex/debugger.md

@@ -64,3 +64,11 @@ You are a senior debugging specialist focusing on backend systems, API issues, d
 ### Probable Root Cause
 [Conclusion with reasoning]
 ```
+
+## .context Awareness
+
+If the project has a `.context/` directory:
+1. Read `.context/prefs/workflow.md` for project-specific debugging rules
+2. Check `.context/history/commits.jsonl` for past bugs on related files — search `bugs[]` and `changes.files` fields
+3. Past decision context (assumptions, rejected alternatives) may reveal why code was written a certain way
+4. Document your diagnosis clearly: symptom, root cause, fix, and lesson learned (will be captured for future context)

package/templates/prompts/codex/optimizer.md

@@ -72,3 +72,10 @@ You are a senior performance engineer specializing in backend optimization, data
 - Expected After: [metrics]
 - How to measure: [commands/tools]
 ```
+
+## .context Awareness
+
+If the project has a `.context/` directory:
+1. Read `.context/prefs/coding-style.md` for project performance conventions
+2. Check `.context/history/commits.jsonl` for past optimization decisions — avoid re-doing work or reverting previous optimizations without reason
+3. Document optimization trade-offs clearly in your output (will be captured for future context)

package/templates/prompts/codex/reviewer.md

@@ -64,3 +64,10 @@ RECOMMENDATION: [PASS/NEEDS_IMPROVEMENT]
 2. **Critical Issues** - Must fix before merge
 3. **Suggestions** - Nice to have improvements
 4. **Positive Notes** - What's done well
+
+## .context Awareness
+
+If the project has a `.context/` directory:
+1. Read `.context/prefs/coding-style.md` as the primary review standard
+2. Read `.context/prefs/workflow.md` to verify the full development flow was followed (tests written, docs updated, etc.)
+3. Check `.context/history/commits.jsonl` for past decisions on the same files — flag if current changes contradict previous architectural decisions without justification

package/templates/prompts/codex/tester.md

@@ -53,3 +53,10 @@ You are a senior test engineer specializing in backend testing, API testing, and
 2. **Test Cases** - List of scenarios to cover
 3. **Implementation** - Unified Diff Patch for test files
 4. **Coverage Notes** - What's covered and what's not
+
+## .context Awareness
+
+If the project has a `.context/` directory:
+1. Read `.context/prefs/coding-style.md` for testing conventions (naming, patterns, coverage requirements)
+2. Read `.context/prefs/workflow.md` to understand required test flow (e.g., failing test first for bug fixes)
+3. Check `.context/history/commits.jsonl` for past bugs on related files — ensure regression tests cover previously fixed issues

package/templates/prompts/gemini/analyzer.md

@@ -51,3 +51,11 @@ You are a senior UI/UX analyst specializing in design systems, user experience e
 3. **Technical Considerations** - Frontend architecture impact
 4. **Options** - Alternative approaches with trade-offs
 5. **Recommendation** - Preferred approach with rationale
+
+## .context Awareness
+
+If the project has a `.context/` directory:
+1. Read `.context/prefs/coding-style.md` and `.context/prefs/workflow.md` before analysis
+2. Use rules from prefs/ as evaluation criteria
+3. When analyzing, check `.context/history/commits.jsonl` for related past decisions
+4. Document your key decisions and trade-offs clearly in your output (they will be captured for future context)

package/templates/prompts/gemini/architect.md

@@ -45,3 +45,11 @@ You are a senior frontend architect specializing in UI/UX design systems, compon
 2. **Architecture Decision** - Key design choices with rationale
 3. **Implementation Plan** - Step-by-step with pseudo-code
 4. **Considerations** - Performance, accessibility, maintainability notes
+
+## .context Awareness
+
+If the project has a `.context/` directory:
+1. Read `.context/prefs/coding-style.md` and `.context/prefs/workflow.md` before designing
+2. Follow all coding conventions defined in prefs/
+3. Check `.context/history/commits.jsonl` for past architectural decisions on related components
+4. In your Architecture Decision section, clearly state: rationale, rejected alternatives, assumptions, and potential side effects (these will be captured as ContextEntry for future reference)

package/templates/prompts/gemini/debugger.md

@@ -68,3 +68,11 @@ You are a senior frontend debugging specialist focusing on UI issues, component
 ### Probable Root Cause
 [Conclusion with reasoning]
 ```
+
+## .context Awareness
+
+If the project has a `.context/` directory:
+1. Read `.context/prefs/workflow.md` for project-specific debugging rules
+2. Check `.context/history/commits.jsonl` for past bugs on related components — search `bugs[]` and `changes.files` fields
+3. Past decision context (assumptions, rejected alternatives) may reveal why UI was built a certain way
+4. Document your diagnosis clearly: symptom, root cause, fix, and lesson learned (will be captured for future context)

package/templates/prompts/gemini/frontend.md

@@ -54,3 +54,11 @@ You are a senior frontend developer specializing in React applications, responsi
 2. **Design Decisions** - UI/UX choices with rationale
 3. **Implementation** - Unified Diff Patch
 4. **Usage Example** - How to use the component
+
+## .context Awareness
+
+If the project has a `.context/` directory:
+1. Read `.context/prefs/coding-style.md` and `.context/prefs/workflow.md` before coding
+2. Follow all conventions (naming, patterns, testing requirements)
+3. When making design decisions (choosing component patterns, state management, etc.), clearly state rationale and rejected alternatives in your output
+4. Follow the full development flow from workflow.md (implement → test → docs)

package/templates/prompts/gemini/optimizer.md

@@ -75,3 +75,10 @@ You are a senior frontend performance engineer specializing in React optimizatio
 - Expected after: [score]
 - How to measure: [tools]
 ```
+
+## .context Awareness
+
+If the project has a `.context/` directory:
+1. Read `.context/prefs/coding-style.md` for project performance conventions
+2. Check `.context/history/commits.jsonl` for past optimization decisions — avoid re-doing work or reverting previous optimizations without reason
+3. Document optimization trade-offs clearly in your output (will be captured for future context)

package/templates/prompts/gemini/reviewer.md

@@ -71,3 +71,10 @@ RECOMMENDATION: [PASS/NEEDS_IMPROVEMENT]
 3. **Design Issues** - Inconsistencies
 4. **Suggestions** - Improvements
 5. **Positive Notes** - What's done well
+
+## .context Awareness
+
+If the project has a `.context/` directory:
+1. Read `.context/prefs/coding-style.md` as the primary review standard
+2. Read `.context/prefs/workflow.md` to verify the full development flow was followed (tests written, docs updated, etc.)
+3. Check `.context/history/commits.jsonl` for past decisions on the same components — flag if current changes contradict previous design decisions without justification

package/templates/prompts/gemini/tester.md

@@ -59,3 +59,10 @@ You are a senior test engineer specializing in frontend testing, component testi
 2. **Test Cases** - Scenarios to cover
 3. **Implementation** - Unified Diff Patch for test files
 4. **Accessibility Notes** - a11y test coverage
+
+## .context Awareness
+
+If the project has a `.context/` directory:
+1. Read `.context/prefs/coding-style.md` for testing conventions (naming, patterns, coverage requirements)
+2. Read `.context/prefs/workflow.md` to understand required test flow (e.g., failing test first for bug fixes)
+3. Check `.context/history/commits.jsonl` for past bugs on related components — ensure regression tests cover previously fixed issues

package/templates/rules/ccg-skills.md

@@ -0,0 +1,63 @@
+# CCG Quality Gates — Auto-trigger Rules
+
+When working in a project, automatically invoke the corresponding quality gate skills based on the scenario below. These skills are installed at `~/.claude/skills/ccg/` and can be called directly.
+
+## Trigger Rules
+
+### New Module Created
+
+When a new module/package/directory is created with source code:
+
+```
+/gen-docs <module-path>        → Generate README.md + DESIGN.md skeleton
+  ↓ (after development)
+/verify-module <module-path>   → Check structure completeness
+  ↓
+/verify-security <module-path> → Scan for security vulnerabilities
+```
+
+### Code Changes > 30 Lines
+
+When a single task produces code changes exceeding 30 lines:
+
+```
+/verify-change                 → Analyze change impact, check doc sync
+  ↓
+/verify-quality <changed-path> → Check complexity, code smells, naming
+```
+
+### Security-Related Changes
+
+When changes involve authentication, authorization, encryption, input validation, or secrets management:
+
+```
+/verify-security <changed-path> → Scan for vulnerabilities
+```
+
+### Refactoring
+
+When refactoring existing code:
+
+```
+/verify-change                  → Ensure docs reflect the refactoring
+  ↓
+/verify-quality <refactored-path> → Verify quality improved
+  ↓
+/verify-security <refactored-path> → No new vulnerabilities introduced
+```
+
+## Execution Rules
+
+1. **Non-blocking** — Quality gates produce reports but do NOT block delivery unless Critical issues are found
+2. **Chainable** — Run gates in the order specified above; skip if previous gate fails
+3. **Silent on pass** — Only report findings; do not output "all clear" messages for every gate
+4. **Critical = must fix** — Only `Critical` / `High` severity findings require action before delivery
+5. **Idempotent** — Safe to re-run; same input produces same output
+
+## Multi-Agent Coordination
+
+When a task involves 3+ independent files/modules or 2+ parallel workflows, refer to the multi-agent orchestration skill at `~/.claude/skills/ccg/orchestration/multi-agent/SKILL.md` for:
+
+- Agent role assignment (Lead / Scout / Worker / Soldier / Drone)
+- File ownership locking (one writer per file at any time)
+- Task decomposition strategy (by file, by module, or by pipeline)