@jspg-ai/coding-bb 0.0.3-beta.1 → 0.0.3-beta.12

package/superpowers/skills/writing-skills/graphviz-conventions.dot

@@ -1,172 +1,172 @@
-digraph STYLE_GUIDE {
-    // The style guide for our process DSL, written in the DSL itself
-
-    // Node type examples with their shapes
-    subgraph cluster_node_types {
-        label="NODE TYPES AND SHAPES";
-
-        // Questions are diamonds
-        "Is this a question?" [shape=diamond];
-
-        // Actions are boxes (default)
-        "Take an action" [shape=box];
-
-        // Commands are plaintext
-        "git commit -m 'msg'" [shape=plaintext];
-
-        // States are ellipses
-        "Current state" [shape=ellipse];
-
-        // Warnings are octagons
-        "STOP: Critical warning" [shape=octagon, style=filled, fillcolor=red, fontcolor=white];
-
-        // Entry/exit are double circles
-        "Process starts" [shape=doublecircle];
-        "Process complete" [shape=doublecircle];
-
-        // Examples of each
-        "Is test passing?" [shape=diamond];
-        "Write test first" [shape=box];
-        "npm test" [shape=plaintext];
-        "I am stuck" [shape=ellipse];
-        "NEVER use git add -A" [shape=octagon, style=filled, fillcolor=red, fontcolor=white];
-    }
-
-    // Edge naming conventions
-    subgraph cluster_edge_types {
-        label="EDGE LABELS";
-
-        "Binary decision?" [shape=diamond];
-        "Yes path" [shape=box];
-        "No path" [shape=box];
-
-        "Binary decision?" -> "Yes path" [label="yes"];
-        "Binary decision?" -> "No path" [label="no"];
-
-        "Multiple choice?" [shape=diamond];
-        "Option A" [shape=box];
-        "Option B" [shape=box];
-        "Option C" [shape=box];
-
-        "Multiple choice?" -> "Option A" [label="condition A"];
-        "Multiple choice?" -> "Option B" [label="condition B"];
-        "Multiple choice?" -> "Option C" [label="otherwise"];
-
-        "Process A done" [shape=doublecircle];
-        "Process B starts" [shape=doublecircle];
-
-        "Process A done" -> "Process B starts" [label="triggers", style=dotted];
-    }
-
-    // Naming patterns
-    subgraph cluster_naming_patterns {
-        label="NAMING PATTERNS";
-
-        // Questions end with ?
-        "Should I do X?";
-        "Can this be Y?";
-        "Is Z true?";
-        "Have I done W?";
-
-        // Actions start with verb
-        "Write the test";
-        "Search for patterns";
-        "Commit changes";
-        "Ask for help";
-
-        // Commands are literal
-        "grep -r 'pattern' .";
-        "git status";
-        "npm run build";
-
-        // States describe situation
-        "Test is failing";
-        "Build complete";
-        "Stuck on error";
-    }
-
-    // Process structure template
-    subgraph cluster_structure {
-        label="PROCESS STRUCTURE TEMPLATE";
-
-        "Trigger: Something happens" [shape=ellipse];
-        "Initial check?" [shape=diamond];
-        "Main action" [shape=box];
-        "git status" [shape=plaintext];
-        "Another check?" [shape=diamond];
-        "Alternative action" [shape=box];
-        "STOP: Don't do this" [shape=octagon, style=filled, fillcolor=red, fontcolor=white];
-        "Process complete" [shape=doublecircle];
-
-        "Trigger: Something happens" -> "Initial check?";
-        "Initial check?" -> "Main action" [label="yes"];
-        "Initial check?" -> "Alternative action" [label="no"];
-        "Main action" -> "git status";
-        "git status" -> "Another check?";
-        "Another check?" -> "Process complete" [label="ok"];
-        "Another check?" -> "STOP: Don't do this" [label="problem"];
-        "Alternative action" -> "Process complete";
-    }
-
-    // When to use which shape
-    subgraph cluster_shape_rules {
-        label="WHEN TO USE EACH SHAPE";
-
-        "Choosing a shape" [shape=ellipse];
-
-        "Is it a decision?" [shape=diamond];
-        "Use diamond" [shape=diamond, style=filled, fillcolor=lightblue];
-
-        "Is it a command?" [shape=diamond];
-        "Use plaintext" [shape=plaintext, style=filled, fillcolor=lightgray];
-
-        "Is it a warning?" [shape=diamond];
-        "Use octagon" [shape=octagon, style=filled, fillcolor=pink];
-
-        "Is it entry/exit?" [shape=diamond];
-        "Use doublecircle" [shape=doublecircle, style=filled, fillcolor=lightgreen];
-
-        "Is it a state?" [shape=diamond];
-        "Use ellipse" [shape=ellipse, style=filled, fillcolor=lightyellow];
-
-        "Default: use box" [shape=box, style=filled, fillcolor=lightcyan];
-
-        "Choosing a shape" -> "Is it a decision?";
-        "Is it a decision?" -> "Use diamond" [label="yes"];
-        "Is it a decision?" -> "Is it a command?" [label="no"];
-        "Is it a command?" -> "Use plaintext" [label="yes"];
-        "Is it a command?" -> "Is it a warning?" [label="no"];
-        "Is it a warning?" -> "Use octagon" [label="yes"];
-        "Is it a warning?" -> "Is it entry/exit?" [label="no"];
-        "Is it entry/exit?" -> "Use doublecircle" [label="yes"];
-        "Is it entry/exit?" -> "Is it a state?" [label="no"];
-        "Is it a state?" -> "Use ellipse" [label="yes"];
-        "Is it a state?" -> "Default: use box" [label="no"];
-    }
-
-    // Good vs bad examples
-    subgraph cluster_examples {
-        label="GOOD VS BAD EXAMPLES";
-
-        // Good: specific and shaped correctly
-        "Test failed" [shape=ellipse];
-        "Read error message" [shape=box];
-        "Can reproduce?" [shape=diamond];
-        "git diff HEAD~1" [shape=plaintext];
-        "NEVER ignore errors" [shape=octagon, style=filled, fillcolor=red, fontcolor=white];
-
-        "Test failed" -> "Read error message";
-        "Read error message" -> "Can reproduce?";
-        "Can reproduce?" -> "git diff HEAD~1" [label="yes"];
-
-        // Bad: vague and wrong shapes
-        bad_1 [label="Something wrong", shape=box];  // Should be ellipse (state)
-        bad_2 [label="Fix it", shape=box];  // Too vague
-        bad_3 [label="Check", shape=box];  // Should be diamond
-        bad_4 [label="Run command", shape=box];  // Should be plaintext with actual command
-
-        bad_1 -> bad_2;
-        bad_2 -> bad_3;
-        bad_3 -> bad_4;
-    }
+digraph STYLE_GUIDE {
+    // The style guide for our process DSL, written in the DSL itself
+
+    // Node type examples with their shapes
+    subgraph cluster_node_types {
+        label="NODE TYPES AND SHAPES";
+
+        // Questions are diamonds
+        "Is this a question?" [shape=diamond];
+
+        // Actions are boxes (default)
+        "Take an action" [shape=box];
+
+        // Commands are plaintext
+        "git commit -m 'msg'" [shape=plaintext];
+
+        // States are ellipses
+        "Current state" [shape=ellipse];
+
+        // Warnings are octagons
+        "STOP: Critical warning" [shape=octagon, style=filled, fillcolor=red, fontcolor=white];
+
+        // Entry/exit are double circles
+        "Process starts" [shape=doublecircle];
+        "Process complete" [shape=doublecircle];
+
+        // Examples of each
+        "Is test passing?" [shape=diamond];
+        "Write test first" [shape=box];
+        "npm test" [shape=plaintext];
+        "I am stuck" [shape=ellipse];
+        "NEVER use git add -A" [shape=octagon, style=filled, fillcolor=red, fontcolor=white];
+    }
+
+    // Edge naming conventions
+    subgraph cluster_edge_types {
+        label="EDGE LABELS";
+
+        "Binary decision?" [shape=diamond];
+        "Yes path" [shape=box];
+        "No path" [shape=box];
+
+        "Binary decision?" -> "Yes path" [label="yes"];
+        "Binary decision?" -> "No path" [label="no"];
+
+        "Multiple choice?" [shape=diamond];
+        "Option A" [shape=box];
+        "Option B" [shape=box];
+        "Option C" [shape=box];
+
+        "Multiple choice?" -> "Option A" [label="condition A"];
+        "Multiple choice?" -> "Option B" [label="condition B"];
+        "Multiple choice?" -> "Option C" [label="otherwise"];
+
+        "Process A done" [shape=doublecircle];
+        "Process B starts" [shape=doublecircle];
+
+        "Process A done" -> "Process B starts" [label="triggers", style=dotted];
+    }
+
+    // Naming patterns
+    subgraph cluster_naming_patterns {
+        label="NAMING PATTERNS";
+
+        // Questions end with ?
+        "Should I do X?";
+        "Can this be Y?";
+        "Is Z true?";
+        "Have I done W?";
+
+        // Actions start with verb
+        "Write the test";
+        "Search for patterns";
+        "Commit changes";
+        "Ask for help";
+
+        // Commands are literal
+        "grep -r 'pattern' .";
+        "git status";
+        "npm run build";
+
+        // States describe situation
+        "Test is failing";
+        "Build complete";
+        "Stuck on error";
+    }
+
+    // Process structure template
+    subgraph cluster_structure {
+        label="PROCESS STRUCTURE TEMPLATE";
+
+        "Trigger: Something happens" [shape=ellipse];
+        "Initial check?" [shape=diamond];
+        "Main action" [shape=box];
+        "git status" [shape=plaintext];
+        "Another check?" [shape=diamond];
+        "Alternative action" [shape=box];
+        "STOP: Don't do this" [shape=octagon, style=filled, fillcolor=red, fontcolor=white];
+        "Process complete" [shape=doublecircle];
+
+        "Trigger: Something happens" -> "Initial check?";
+        "Initial check?" -> "Main action" [label="yes"];
+        "Initial check?" -> "Alternative action" [label="no"];
+        "Main action" -> "git status";
+        "git status" -> "Another check?";
+        "Another check?" -> "Process complete" [label="ok"];
+        "Another check?" -> "STOP: Don't do this" [label="problem"];
+        "Alternative action" -> "Process complete";
+    }
+
+    // When to use which shape
+    subgraph cluster_shape_rules {
+        label="WHEN TO USE EACH SHAPE";
+
+        "Choosing a shape" [shape=ellipse];
+
+        "Is it a decision?" [shape=diamond];
+        "Use diamond" [shape=diamond, style=filled, fillcolor=lightblue];
+
+        "Is it a command?" [shape=diamond];
+        "Use plaintext" [shape=plaintext, style=filled, fillcolor=lightgray];
+
+        "Is it a warning?" [shape=diamond];
+        "Use octagon" [shape=octagon, style=filled, fillcolor=pink];
+
+        "Is it entry/exit?" [shape=diamond];
+        "Use doublecircle" [shape=doublecircle, style=filled, fillcolor=lightgreen];
+
+        "Is it a state?" [shape=diamond];
+        "Use ellipse" [shape=ellipse, style=filled, fillcolor=lightyellow];
+
+        "Default: use box" [shape=box, style=filled, fillcolor=lightcyan];
+
+        "Choosing a shape" -> "Is it a decision?";
+        "Is it a decision?" -> "Use diamond" [label="yes"];
+        "Is it a decision?" -> "Is it a command?" [label="no"];
+        "Is it a command?" -> "Use plaintext" [label="yes"];
+        "Is it a command?" -> "Is it a warning?" [label="no"];
+        "Is it a warning?" -> "Use octagon" [label="yes"];
+        "Is it a warning?" -> "Is it entry/exit?" [label="no"];
+        "Is it entry/exit?" -> "Use doublecircle" [label="yes"];
+        "Is it entry/exit?" -> "Is it a state?" [label="no"];
+        "Is it a state?" -> "Use ellipse" [label="yes"];
+        "Is it a state?" -> "Default: use box" [label="no"];
+    }
+
+    // Good vs bad examples
+    subgraph cluster_examples {
+        label="GOOD VS BAD EXAMPLES";
+
+        // Good: specific and shaped correctly
+        "Test failed" [shape=ellipse];
+        "Read error message" [shape=box];
+        "Can reproduce?" [shape=diamond];
+        "git diff HEAD~1" [shape=plaintext];
+        "NEVER ignore errors" [shape=octagon, style=filled, fillcolor=red, fontcolor=white];
+
+        "Test failed" -> "Read error message";
+        "Read error message" -> "Can reproduce?";
+        "Can reproduce?" -> "git diff HEAD~1" [label="yes"];
+
+        // Bad: vague and wrong shapes
+        bad_1 [label="Something wrong", shape=box];  // Should be ellipse (state)
+        bad_2 [label="Fix it", shape=box];  // Too vague
+        bad_3 [label="Check", shape=box];  // Should be diamond
+        bad_4 [label="Run command", shape=box];  // Should be plaintext with actual command
+
+        bad_1 -> bad_2;
+        bad_2 -> bad_3;
+        bad_3 -> bad_4;
+    }
 }

package/cbb/worktrees/commands/worktree-close.md

@@ -1,64 +0,0 @@
----
-name: "CBB: Worktree Close"
-description: 关闭/清理由 init-worktree 创建的多仓库联动 worktree 工作空间，移除 worktree 并按用户选择处理特性分支
-category: Workflow
-tags: [worktree, cleanup, worktree, git-worktree]
----
-
-# CBB: Worktree Close - 关闭 Worktree
-
-## 重要：第一步必须用 Read 工具直接打开 SKILL.md
-
-**禁止**用 `ls` / `find` / `cat` / `head` / `grep` 等 bash 命令搜索 SKILL.md。这些命令在 Agent 运行环境（Qoder Windows PowerShell 等）中经常失败。
-
-**直接路径**：
-- Qoder 适配器：`.qoder/skills/cbb-worktree-close/SKILL.md`
-- Claude Code 适配器：`.claude/skills/cbb-worktree-close/SKILL.md`
-
-**第一步**：
-1. 用 Read 工具直接打开 SKILL.md
-2. 按 SKILL.md 的 Step 0 → 1 → 2 → 3 → 4 → 5 → 6 顺序执行
-3. 每次调用 Node.js 脚本时使用**绝对路径**
-
-## Input
-
-参数 `<分支名>`（可选），指定要关闭的 worktree 对应的特性分支。**未提供时按 SKILL.md Step 1 在对话中询问或自动选取唯一 worktree**。
-
-**Steps 概述**（完整流程见 SKILL.md）
-
-1. Step 0：前置校验（Git 仓库检测、workspace-config.json 检测，支持向上查找）
-2. Step 1：确定要关闭的目标 worktree（列出 `.worktrees/` 下的工作空间 worktree，用户选择或自动选取）
-3. Step 2：发现关联应用 worktree（读 workspace-config.json，按实际存在性确定关联清单）
-4. Step 3：安全检查（未提交修改 / 是否合并到主分支 / 是否推到远程，含主动 fetch 刷新远程引用）
-5. Step 4：用户决策（未提交修改处理方式 + 分支处理方式，AskUserQuestion 固定选项）
-6. Step 5：移除 Worktree（三层降级策略：正常移除 → prune+物理删除 → 仅 prune 延迟清理）
-7. Step 5.5：二次确认 worktree 已移除（确保分支不再被检出）
-8. Step 6：删除分支（按用户选择的 MODE：保留 / 删本地 / 删本地+远程）
-9. Step 8：确认收尾（pwd 确认、残留检查、最终报告）
-
-**Output**
-
-```
-✅ 工作空间 worktree 已关闭
-  当前目录：<工作空间根目录绝对路径>
-  已移除 worktree：
-    - .worktrees/worktree-<需求名>（workspace）
-    - .worktrees/worktree-<需求名>/<应用名1>（嵌套）
-    - .worktrees/worktree-<需求名>/<应用名2>（嵌套）
-  未提交修改：已丢弃（--force）/ 无
-  分支处理：<需求名> 已删除（本地+远程）/ 已删除（本地）/ 已保留
-  剩余工作空间 worktree：<列出仍存在的，或 "无" >
-  Workspace cleaned up.
-```
-
-详细输出格式与安全检查报告，见 SKILL.md「最终报告」与「Step 3」段。
-
-**Guardrails**
-
-- 必须在业务工作空间根目录执行（包含 workspace-config.json 的目录），支持从 worktree 内部向上查找
-- 顺序硬约束：**先移除所有 worktree，再删除分支**（先删分支会报 `Cannot delete branch checked out at`）
-- 破坏性操作必须先报告、经用户确认才执行（未提交修改、未合并分支绝不静默 `--force` 或 `-D`）
-- 只操作 `.worktrees/worktree-<需求名>` 路径，绝不碰其它 worktree（如 IDE 会话 worktree）
-- 关联应用以实际存在的 worktree 为准，不假设 workspace-config.json 中所有应用都有关联
-- 依赖 shell 函数的脚本必须整段在一次 Bash 调用中执行（函数不跨调用保留）
-- git 操作一律用 `git -C <仓库>` 绝对路径，不依赖跨调用的 cwd

package/cbb/worktrees/commands/worktree-init.md

@@ -1,51 +0,0 @@
----
-name: "CBB: Worktree Init"
-description: 为一个需求在 workspace 与各关联应用仓库同步创建同名 git worktree，物理直聚在 `.worktrees/<需求名>/` 目录
-category: Workflow
-tags: [worktree, isolation, worktree, git-worktree]
----
-
-# CBB: Worktree Init - 创建 Worktree
-
-## 重要：第一步必须用 Read 工具直接打开 SKILL.md
-
-**禁止**用 `ls` / `find` / `cat` / `head` / `grep` 等 bash 命令搜索 SKILL.md 是否存在。**这些命令在 Agent 运行环境（Qoder Windows PowerShell 等）中经常失败**（如 `head` 不存在、stderr 重定向无效等）。
-
-**直接路径**：
-- Qoder 适配器：`.qoder/skills/cbb-worktree-init/SKILL.md`
-- Claude Code 适配器：`.claude/skills/cbb-worktree-init/SKILL.md`
-
-**第一步**：
-1. 用 Read 工具直接打开 `.qoder/skills/cbb-worktree-init/SKILL.md`（或 `.claude/skills/...`）
-2. 按 SKILL.md 的 Step 0 → 1 → 2 → 3 → 4 顺序执行
-3. 每次调用 Node.js 脚本时，使用**绝对路径**（避免依赖相对路径）：
-   ```
-   node "D:\workspace\<用户工作空间>\.qoder\skills\cbb-worktree-init\scripts\<name>.js" <参数>
-   ```
-   - 参数形式：
-     - `check-env.js`：无参数
-     - `parse-config.js`：无参数
-     - `sync-repos.js`：`<ws_root>`
-     - `check-repos.js`：`<ws_root>`
-     - `create-branches.js`：`<ws_root> <branch>`
-     - `update-gitignore.js`：`<ws_root> <branch>`
-      - `create-worktrees.js`：`<ws_root> <branch>`
-
-## Input
-
-参数 `<需求名>`（kebab-case），同时作分支名和 workspace 工作树目录名。**未提供时按 SKILL.md Step 3.1 在对话中询问**。
-
-## 流程总览（完整流程见 SKILL.md）
-
-1. Step 0：环境探活 + 解析 workspace-config.json
-2. Step 1：同步 .codespace/ 仓库（fetch --all）
-3. Step 2：状态检查（5 项 / 3 项分级）
-4. Step 3：创建分支 → 推送 upstream → 创建 worktree（workspace + 嵌套 app）
-5. Step 4：收尾与交接（继续当前会话，声明目录纪律）
-
-## 关键 Guardrails
-
-- workspace 主分支 tracked 的所有内容（openspec/、cbb/ 等）由 git worktree 自动 checkout——**禁止 cp / clone / symlink “带过来”**
-- 必须用 `git branch` 而非 `git checkout -b`（分支不能同时在主目录与 worktree 检出）
-- 运行环境 node 不可用时 fail-fast：终止流程并提示用户到系统终端重试
-- **不要试图搜索 SKILL.md**——直接用 Read 工具打开

package/cbb/worktrees/commands/worktree-push.md

@@ -1,42 +0,0 @@
----
-name: "CBB: Worktree Push"
-description: 跨 worktree 提交并推送当前需求的所有关联仓库到 origin
-category: Workflow
-tags: [workflow, push, commit, worktree, experimental]
----
-
-跨 worktree 提交并推送当前需求的所有关联仓库到 origin。
-
-**Input**: 可选指定需求名（如 `/cbb:worktree-push ft-diff-on-cargo`）。省略时从 cwd 的 `.worktrees/worktree-<需求名>/` 路径推断（cwd 在工作空间根目录时由 Step 0 定位）。
-
-**何时使用**：
-
-- apply 完成后准备推送所有改动
-- close-worktree 前需要先确保 ahead 提交已推送（避免丢）
-- 开发过程中想保存中间进度
-- 用户口语化说"提交并push" / "推一下"
-
-**Steps 摘要**（详细见 [cbb-worktree-push SKILL.md](../../skills/cbb-worktree-push/SKILL.md)）：
-
-1. **Step 0**：定位工作空间根（find-workspace-root.js）
-2. **Step 1**：识别目标 worktree（find-target-worktree.js）
-3. **Step 2**：扫描所有 worktree 仓库状态（commit-worktrees.js --dry-run）
-4. **Step 3**：对话中收集 commit 信息（必须由用户提供）
-5. **Step 4**：批量 commit（commit-worktrees.js）
-6. **Step 5**：批量 push（push-worktrees.js）
-7. **Step 6**：汇总报告
-
-**关键 Guardrails**：
-
-- 严格按 Step 0 → 1 → 2 → 3 → 4 → 5 → 6 顺序执行
-- **Step 2 dry-run 必跑**，让用户看到将要 commit 的内容
-- **Step 3 必问用户 commit 信息**（自由文本），禁止自动生成
-- 默认 `git add -u`（仅 tracked），避免误纳未追踪文件
-- push 失败时阻塞并按错误码分类处理，**禁止**自动跳过失败仓库
-- 远程分支已存在时必须输出 commit 元信息再询问用户决策
-
-**Failure Handling**：
-
-- commit-worktrees.js 退出码 2 → 部分 commit 失败，**阻塞流程**，询问用户
-- push-worktrees.js 退出码 2 → 部分 push 失败，**阻塞流程**，按错误码询问用户
-- 远程分支已存在 → 先输出元信息，再 AskUserQuestion 让用户选择「关联」或「终止」