[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7APSHTPWJMMSTAESZBF3RFK":3,"skill-same:01M7APSHTPWJMMSTAESZBF3RFK":51},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":29,"commitSha":30,"skillDirectory":31,"forksCount":14,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":34,"ownerDescription":35,"updatedAt":36,"install":37,"resources":50},"01M7APSHTPWJMMSTAESZBF3RFK","fresh-context-review",null,"Author-triggered fresh-context scan of PR diff before formal review. Finding generator, NOT approval authority. Use when: quality-gate 通过、PR 非 trivial、想降低正式 reviewer 认知负荷。 Not for: 正式 review verdict、approval、merge decision。 Output: Finding list（附在 review request 中）。","peps1666\u002FBuildCrew-AI","peps1666","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128503359?v=4","01M7APD9BQ6NTJ79J9FTB6YZGT","junhao zhou","01M7APD9CD06Q6CCJ22FYVG2AK",0,"MIT","https:\u002F\u002Fgithub.com\u002Fpeps1666\u002FBuildCrew-AI\u002Fblob\u002Fmain\u002Fcat-cafe-skills\u002Ffresh-context-review\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: fresh-context-review\ndescription: >\n  Author-triggered fresh-context scan of PR diff before formal review.\n  Finding generator, NOT approval authority.\n  Use when: quality-gate 通过、PR 非 trivial、想降低正式 reviewer 认知负荷。\n  Not for: 正式 review verdict、approval、merge decision。\n  Output: Finding list（附在 review request 中）。\ntriggers:\n  - \"fresh context\"\n  - \"pre-review scan\"\n  - \"找新眼看看\"\n---\n\n> **SOP 位置**: 可选步骤，在 `quality-gate` (Step ②) 之后、`request-review` (Step ③a) 之前。\n> **SOP definition**: `sop-definitions\u002Fdevelopment.yaml` stage `fresh_context`（optional）。\n> **上一步**: `quality-gate` | **下一步**: `request-review`\n\n# Fresh-Context Pre-Review\n\n在正式 cross-cat review 前，用一个 **fresh-context session**（没参与开发的猫或 author 的新 session）扫一遍 PR diff，产出 finding list。目的是**降低正式 reviewer 的认知负荷**——reviewer 可以先看 fresh-context findings 再看 diff，节约时间聚焦深层问题。\n\n## ⚠️ 身份约束（硬规则 — Non-Goal #4）\n\n**This is a FINDING GENERATOR, not an approval authority.**\n\n- ❌ 不产出 APPROVE \u002F BLOCK \u002F LGTM verdict\n- ❌ 不替代 Layer 2\u002F3 named cat review\n- ❌ 不签署任何 merge-gate 可识别的放行信号\n- ❌ 不影响 Review Provenance Matrix（不产生 localPeerReviewSha \u002F cloudReviewSha）\n- ✅ 只产出 \"我看到这些 findings\"（带签名的 finding list）\n\n## 核心知识\n\n### 触发决策表\n\n| PR 类型 | 触发？ | 理由 |\n|---------|--------|------|\n| 多文件代码改动（≥3 files, ≥50 行 diff） | ✅ 推荐 | 正式 reviewer 认知负荷高 |\n| shared\u002F 或跨包改动 | ✅ 推荐 | 影响面广，early detection 价值高 |\n| 状态机 \u002F 生命周期对象改动 | ✅ 推荐 | 转移边容易漏（F229 教训） |\n| 纯文档 \u002F ≤10 行 \u002F typo | ❌ 跳过 | 认知负荷已经很低 |\n| SKILL.md-only | ❌ 跳过 | 轻量改动，正式 reviewer 足以覆盖 |\n| 紧急 hotfix | ❌ 跳过 | 时间约束优先 |\n\n**决策权在 author**：表格是建议，不是硬规则。Author 自判是否需要 fresh context。\n\n### 盲点正交性（cross-model 价值）\n\n不同模型族有不同的系统性盲点：\n\n- Claude 族（Ragdoll）的盲点 ≠ GPT 族（Maine Coon）的盲点\n- 跨族 fresh-context 的 finding yield > 同族 fresh-context\n- 这正是 **reviewer delta metric**（AC-B2）要量化的价值\n\n## 流程\n\n### 前置条件\n\n| 条件 | 检查方式 | 未满足时 |\n|------|----------|----------|\n| `quality-gate` 已通过 | 有本轮 gate report | 先跑 quality-gate |\n| PR diff 存在 | `git diff origin\u002Fmain...HEAD` 有输出 | 没改东西不需要 review |\n| Author 判断需要 | 查触发决策表 | 跳过，直接进 request-review |\n\n### Ownership: Author 触发\n\n```\n1. Author 完成开发，quality-gate ✅\n2. Author 判断是否需要 fresh-context（查触发决策表）\n3. 需要 → Author 触发 fresh-context session（见下方 \"如何触发\"）\n4. 不需要 → 直接进 request-review\n```\n\n### 如何触发\n\n**方式 A: @ 另一只猫（推荐 — 盲点正交性更高）**\n\n在当前 thread @ 一只没参与开发的猫，附上 diff 和 spec：\n\n```\n@{reviewer-handle}\n\n请帮忙做一次 fresh-context pre-review scan：\n\nBranch: {branch-name}\nDiff: `git diff origin\u002Fmain...HEAD`\nSpec: `docs\u002Ffeatures\u002FF{NNN}-xxx.md`\nPlan: `feature-specs\u002FYYYY-MM-DD-xxx.md`\n\n只需要产出 finding list，不需要 verdict。\n格式见 cat-cafe-skills\u002Ffresh-context-review\u002FSKILL.md \"Finding List 格式\"。\n```\n\n优先跨 family（Ragdoll写的 → @ Maine Coon扫）。\n同 family 不同个体也可（opus 写的 → @ sonnet 扫）。\n\n**方式 B: Author 自己的新 session（降级方案）**\n\n如果没有其他猫可用，author 可以在一个**全新的 session** 中自己扫——关键是 fresh context（新 session 没有开发过程的上下文污染）。\n\n注意：方式 B 的盲点正交性为零（同 model 同 prompt），finding yield 预期低于方式 A。\n\n### Fresh-Context Agent 的工作\n\n收到 author 请求后：\n\n1. 读 PR diff（`git diff origin\u002Fmain...HEAD`）\n2. 读相关 spec \u002F plan（路径由 author 提供）\n3. 逐文件扫描，关注：\n   - correctness（逻辑正确性、边界条件）\n   - spec-mismatch（实现与 spec\u002FAC 不一致）\n   - missing-test（改了行为但没改测试）\n   - security（输入验证、权限检查）\n   - performance（N+1、不必要的序列化）\n   - naming（与 spec 术语不一致）\n4. **不做 verdict** — 只列 findings，带签名\n\n### Finding List 格式\n\n```markdown\n## Fresh-Context Findings\n\nAgent: {cat signature}\nSHA: {HEAD short sha}\nScope: {N} files, {M} lines changed\n\n| # | File | Line | Category | Finding | Severity |\n|---|------|------|----------|---------|----------|\n| FC-1 | src\u002Ffoo.ts | 42 | correctness | 边界条件未处理：`n \u003C 0` 时返回 undefined | P2 |\n| FC-2 | src\u002Fbar.ts | 18 | naming | 变量 `ctx` 与 spec 中的 `context` 不一致 | P3 |\n| FC-3 | test\u002Fbaz.test.ts | — | missing-test | 新增 `processItem()` 但无 error path 测试 | P2 |\n\nTotal: {X} findings ({Y} P1, {Z} P2, {W} P3)\n\n---\n*Finding generator only — not an approval authority. 正式 review verdict 由 request-review 流程中的 named reviewer 产出。*\n```\n\n**Category 枚举**: `correctness` \u002F `performance` \u002F `naming` \u002F `style` \u002F `security` \u002F `spec-mismatch` \u002F `missing-test` \u002F `doc`\n\n**Severity 规则**:\n- P1: 会导致运行时错误 \u002F 数据丢失 \u002F 安全漏洞\n- P2: 逻辑不完整 \u002F 缺测试 \u002F 与 spec 不一致\n- P3: 命名 \u002F 风格 \u002F 文档\n\n### Author 处理 Findings\n\nAuthor 收到 finding list 后：\n\n1. **逐条审视**（fresh-context 可能有假阳性——agent 没有开发上下文）\n2. **有效的** → 修复后 commit，在 review request 中标注 `fixed (commit {sha})`\n3. **无效的** → 在 review request 中标注 `dismissed: {理由}`\n4. **Author 对 findings 有最终决定权**（fresh-context 不是 reviewer，不产生 debt 或 follow-up）\n\n## 和正式 Review 的关系\n\n| 维度 | Fresh-Context | 正式 Review（request-review \u002F receive-review） |\n|------|--------------|-----------------------------------------------|\n| **角色** | Finding generator | Approval authority |\n| **产出** | Finding list | APPROVE \u002F BLOCK verdict |\n| **权力** | 零（建议性） | 完全（merge-gate 可识别） |\n| **触发** | Author 主动 | request-review 流程 |\n| **Ownership** | Author | Reviewer |\n| **对 merge-gate** | 不可见 | localPeerReviewSha \u002F cloudReviewSha |\n| **Delta metric** | 被度量方 | 度量方（标注 FC:covered \u002F FC:new） |\n\n## Common Mistakes\n\n| 错误 | 正确 |\n|------|------|\n| 把 fresh-context 当正式 review，跳过 request-review | fresh-context 只是预扫，正式 review 仍必须走 |\n| Fresh-context agent 给 APPROVE verdict | 只给 finding list，不给 verdict |\n| Reviewer 因为 fresh-context \"已看过\" 就简化 review | Reviewer 独立判断，fresh-context 是参考不是替代 |\n| 所有 PR 都跑 fresh-context | 按触发决策表判断，trivial 跳过 |\n| Fresh-context findings 产生 follow-up \u002F TD \u002F debt | Author 有最终决定权，dismissed = closed |\n| Fresh-context scan 记入 Review Provenance Matrix | 不记入——它不是 review source |\n\n## 下一步\n\nFresh-context findings 处理完 → 直接进 **`request-review`**（SOP Step ③a）。\n在 review request 中附上 fresh-context findings 摘要（见 `refs\u002Freview-request-template.md` 的 \"Fresh-Context Findings\" section）。正式 reviewer 会用 `FC:covered` \u002F `FC:new` 标注自己的 findings（见 `receive-review` skill \"Reviewer Delta Annotation\"）。\n","> **SOP 位置**: 可选步骤，在 `quality-gate` (Step ②) 之后、`request-review` (Step ③a) 之前。\n> **SOP definition**: `sop-definitions\u002Fdevelopment.yaml` stage `fresh_context`（optional）。\n> **上一步**: `quality-gate` | **下一步**: `request-review`\n\n# Fresh-Context Pre-Review\n\n在正式 cross-cat review 前，用一个 **fresh-context session**（没参与开发的猫或 author 的新 session）扫一遍 PR diff，产出 finding list。目的是**降低正式 reviewer 的认知负荷**——reviewer 可以先看 fresh-context findings 再看 diff，节约时间聚焦深层问题。\n\n## ⚠️ 身份约束（硬规则 — Non-Goal #4）\n\n**This is a FINDING GENERATOR, not an approval authority.**\n\n- ❌ 不产出 APPROVE \u002F BLOCK \u002F LGTM verdict\n- ❌ 不替代 Layer 2\u002F3 named cat review\n- ❌ 不签署任何 merge-gate 可识别的放行信号\n- ❌ 不影响 Review Provenance Matrix（不产生 localPeerReviewSha \u002F cloudReviewSha）\n- ✅ 只产出 \"我看到这些 findings\"（带签名的 finding list）\n\n## 核心知识\n\n### 触发决策表\n\n| PR 类型 | 触发？ | 理由 |\n|---------|--------|------|\n| 多文件代码改动（≥3 files, ≥50 行 diff） | ✅ 推荐 | 正式 reviewer 认知负荷高 |\n| shared\u002F 或跨包改动 | ✅ 推荐 | 影响面广，early detection 价值高 |\n| 状态机 \u002F 生命周期对象改动 | ✅ 推荐 | 转移边容易漏（F229 教训） |\n| 纯文档 \u002F ≤10 行 \u002F typo | ❌ 跳过 | 认知负荷已经很低 |\n| SKILL.md-only | ❌ 跳过 | 轻量改动，正式 reviewer 足以覆盖 |\n| 紧急 hotfix | ❌ 跳过 | 时间约束优先 |\n\n**决策权在 author**：表格是建议，不是硬规则。Author 自判是否需要 fresh context。\n\n### 盲点正交性（cross-model 价值）\n\n不同模型族有不同的系统性盲点：\n\n- Claude 族（Ragdoll）的盲点 ≠ GPT 族（Maine Coon）的盲点\n- 跨族 fresh-context 的 finding yield > 同族 fresh-context\n- 这正是 **reviewer delta metric**（AC-B2）要量化的价值\n\n## 流程\n\n### 前置条件\n\n| 条件 | 检查方式 | 未满足时 |\n|------|----------|----------|\n| `quality-gate` 已通过 | 有本轮 gate report | 先跑 quality-gate |\n| PR diff 存在 | `git diff origin\u002Fmain...HEAD` 有输出 | 没改东西不需要 review |\n| Author 判断需要 | 查触发决策表 | 跳过，直接进 request-review |\n\n### Ownership: Author 触发\n\n```\n1. Author 完成开发，quality-gate ✅\n2. Author 判断是否需要 fresh-context（查触发决策表）\n3. 需要 → Author 触发 fresh-context session（见下方 \"如何触发\"）\n4. 不需要 → 直接进 request-review\n```\n\n### 如何触发\n\n**方式 A: @ 另一只猫（推荐 — 盲点正交性更高）**\n\n在当前 thread @ 一只没参与开发的猫，附上 diff 和 spec：\n\n```\n@{reviewer-handle}\n\n请帮忙做一次 fresh-context pre-review scan：\n\nBranch: {branch-name}\nDiff: `git diff origin\u002Fmain...HEAD`\nSpec: `docs\u002Ffeatures\u002FF{NNN}-xxx.md`\nPlan: `feature-specs\u002FYYYY-MM-DD-xxx.md`\n\n只需要产出 finding list，不需要 verdict。\n格式见 cat-cafe-skills\u002Ffresh-context-review\u002FSKILL.md \"Finding List 格式\"。\n```\n\n优先跨 family（Ragdoll写的 → @ Maine Coon扫）。\n同 family 不同个体也可（opus 写的 → @ sonnet 扫）。\n\n**方式 B: Author 自己的新 session（降级方案）**\n\n如果没有其他猫可用，author 可以在一个**全新的 session** 中自己扫——关键是 fresh context（新 session 没有开发过程的上下文污染）。\n\n注意：方式 B 的盲点正交性为零（同 model 同 prompt），finding yield 预期低于方式 A。\n\n### Fresh-Context Agent 的工作\n\n收到 author 请求后：\n\n1. 读 PR diff（`git diff origin\u002Fmain...HEAD`）\n2. 读相关 spec \u002F plan（路径由 author 提供）\n3. 逐文件扫描，关注：\n   - correctness（逻辑正确性、边界条件）\n   - spec-mismatch（实现与 spec\u002FAC 不一致）\n   - missing-test（改了行为但没改测试）\n   - security（输入验证、权限检查）\n   - performance（N+1、不必要的序列化）\n   - naming（与 spec 术语不一致）\n4. **不做 verdict** — 只列 findings，带签名\n\n### Finding List 格式\n\n```markdown\n## Fresh-Context Findings\n\nAgent: {cat signature}\nSHA: {HEAD short sha}\nScope: {N} files, {M} lines changed\n\n| # | File | Line | Category | Finding | Severity |\n|---|------|------|----------|---------|----------|\n| FC-1 | src\u002Ffoo.ts | 42 | correctness | 边界条件未处理：`n \u003C 0` 时返回 undefined | P2 |\n| FC-2 | src\u002Fbar.ts | 18 | naming | 变量 `ctx` 与 spec 中的 `context` 不一致 | P3 |\n| FC-3 | test\u002Fbaz.test.ts | — | missing-test | 新增 `processItem()` 但无 error path 测试 | P2 |\n\nTotal: {X} findings ({Y} P1, {Z} P2, {W} P3)\n\n---\n*Finding generator only — not an approval authority. 正式 review verdict 由 request-review 流程中的 named reviewer 产出。*\n```\n\n**Category 枚举**: `correctness` \u002F `performance` \u002F `naming` \u002F `style` \u002F `security` \u002F `spec-mismatch` \u002F `missing-test` \u002F `doc`\n\n**Severity 规则**:\n- P1: 会导致运行时错误 \u002F 数据丢失 \u002F 安全漏洞\n- P2: 逻辑不完整 \u002F 缺测试 \u002F 与 spec 不一致\n- P3: 命名 \u002F 风格 \u002F 文档\n\n### Author 处理 Findings\n\nAuthor 收到 finding list 后：\n\n1. **逐条审视**（fresh-context 可能有假阳性——agent 没有开发上下文）\n2. **有效的** → 修复后 commit，在 review request 中标注 `fixed (commit {sha})`\n3. **无效的** → 在 review request 中标注 `dismissed: {理由}`\n4. **Author 对 findings 有最终决定权**（fresh-context 不是 reviewer，不产生 debt 或 follow-up）\n\n## 和正式 Review 的关系\n\n| 维度 | Fresh-Context | 正式 Review（request-review \u002F receive-review） |\n|------|--------------|-----------------------------------------------|\n| **角色** | Finding generator | Approval authority |\n| **产出** | Finding list | APPROVE \u002F BLOCK verdict |\n| **权力** | 零（建议性） | 完全（merge-gate 可识别） |\n| **触发** | Author 主动 | request-review 流程 |\n| **Ownership** | Author | Reviewer |\n| **对 merge-gate** | 不可见 | localPeerReviewSha \u002F cloudReviewSha |\n| **Delta metric** | 被度量方 | 度量方（标注 FC:covered \u002F FC:new） |\n\n## Common Mistakes\n\n| 错误 | 正确 |\n|------|------|\n| 把 fresh-context 当正式 review，跳过 request-review | fresh-context 只是预扫，正式 review 仍必须走 |\n| Fresh-context agent 给 APPROVE verdict | 只给 finding list，不给 verdict |\n| Reviewer 因为 fresh-context \"已看过\" 就简化 review | Reviewer 独立判断，fresh-context 是参考不是替代 |\n| 所有 PR 都跑 fresh-context | 按触发决策表判断，trivial 跳过 |\n| Fresh-context findings 产生 follow-up \u002F TD \u002F debt | Author 有最终决定权，dismissed = closed |\n| Fresh-context scan 记入 Review Provenance Matrix | 不记入——它不是 review source |\n\n## 下一步\n\nFresh-context findings 处理完 → 直接进 **`request-review`**（SOP Step ③a）。\n在 review request 中附上 fresh-context findings 摘要（见 `refs\u002Freview-request-template.md` 的 \"Fresh-Context Findings\" section）。正式 reviewer 会用 `FC:covered` \u002F `FC:new` 标注自己的 findings（见 `receive-review` skill \"Reviewer Delta Annotation\"）。\n",{"name":5,"triggers":24,"description":28},[25,26,27],"fresh context","pre-review scan","找新眼看看","Author-triggered fresh-context scan of PR diff before formal review. Finding generator, NOT approval authority. Use when: quality-gate 通过、PR 非 trivial、想降低正式 reviewer 认知负荷。 Not for: 正式 review verdict、approval、merge decision。 Output: Finding list（附在 review request 中）。\n","main","e43f83d5ceb309323cae7e0f31e5e48fd816a57d","cat-cafe-skills\u002Ffresh-context-review","https:\u002F\u002Fgithub.com\u002Fpeps1666\u002FBuildCrew-AI","https:\u002F\u002Fgithub.com\u002Fpeps1666","https:\u002F\u002Fwww.cug.edu.cn\u002F","My name is Zhou Junhao, and I am from China University of Geosciences (Wuhan). My major is Resources and Environment, and my research direction is Remote Sensin","2026-08-16 00:25:38",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add peps1666\u002FBuildCrew-AI --skill fresh-context-review",{"tool":43,"command":44},"bunx","bunx skills add peps1666\u002FBuildCrew-AI --skill fresh-context-review",{"tool":46,"command":47},"pnpm","pnpm dlx skills add peps1666\u002FBuildCrew-AI --skill fresh-context-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fpeps1666\u002FBuildCrew-AI\u002Fblob\u002Fmain\u002Fcat-cafe-skills\u002Ffresh-context-review\u002FSKILL.md",true,[],[52,58,65,72,79,86],{"skillNo":53,"name":54,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M7APYYSHV2SSSRV5Q15JWWPF","plugin-reconcile-skill","https:\u002F\u002Fgithub.com\u002Fpeps1666\u002FBuildCrew-AI\u002Fblob\u002Fmain\u002Fplugins\u002Ftest-reconcile-plugin-regr\u002Fskills\u002Fplugin-reconcile-skill\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7APYWAJ119TPF079F2AXWAS","weixin-mp","通过 Limb 体系操作微信公众号：发布文章、上传图片、管理草稿。 Use when: 需要发布内容到微信公众号、查看草稿、检查公众号连接状态。 Not for: 其他平台的发布、纯文本聊天、非公众号相关操作。 Output: 微信公众号操作结果（发布ID、草稿列表、图片URL等）。","https:\u002F\u002Fgithub.com\u002Fpeps1666\u002FBuildCrew-AI\u002Fblob\u002Fmain\u002Fpackages\u002Fapi\u002Fsrc\u002Fplugins\u002Fweixin-mp\u002Fskills\u002Fweixin-mp\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7APYNNEMBP2T62WT0JT7GNE","writing-skills","创建或修改 Clowder AI skill \u002F MCP tool description 的元技能（含质量标准、范本、发布）。 Use when: 写新 skill、修改现有 skill、写\u002F改 MCP tool description、验证 skill 质量； 或者功能实现中产出了 SKILL.md \u002F cat-cafe-skills\u002F 新目录 \u002F manifest.yaml skill 条目。 Not for: 使用 skill（直接触发对应 skill）。 Output: 新\u002F更新的 SKILL.md + manifest 条目 + symlinks。 GOTCHA: 软硬同重——skill\u002FMCP 质量 = 代码质量；不要写模型已知的通用教程，先过价值门禁。","https:\u002F\u002Fgithub.com\u002Fpeps1666\u002FBuildCrew-AI\u002Fblob\u002Fmain\u002Fcat-cafe-skills\u002Fwriting-skills\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7APYHJDXRH9EDP5D3JZHSVN","writing-plans","将 spec\u002F需求拆分为可执行的分步实施计划。 Use when: 有 spec 或需求，准备动手前需要拆分步骤。 Not for: trivial 改动（≤5 行）、已有详细计划。 Output: 分步实施计划（含 TDD 步骤和检查点）。","https:\u002F\u002Fgithub.com\u002Fpeps1666\u002FBuildCrew-AI\u002Fblob\u002Fmain\u002Fcat-cafe-skills\u002Fwriting-plans\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7APYD2SSZ6Y6CF5SD3YZ5C0","worktree","为代码、脚本、API 与第一方执行面创建隔离 Git worktree，并配置 Redis 6398；classifier 放行的 co-creation docs direct push 不进入本流程。","https:\u002F\u002Fgithub.com\u002Fpeps1666\u002FBuildCrew-AI\u002Fblob\u002Fmain\u002Fcat-cafe-skills\u002Fworktree\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7APY8R4E7RR2WZVPH9V8WWP","workspace-navigator","猫猫把“打开文档、代码或日志”等模糊意图解析成本地绝对路径或 worktree 相对路径，并返回 applied、queued、blocked 或 unconfirmed 的真实 Workspace 投递状态。","https:\u002F\u002Fgithub.com\u002Fpeps1666\u002FBuildCrew-AI\u002Fblob\u002Fmain\u002Fcat-cafe-skills\u002Fworkspace-navigator\u002FSKILL.md",[],[]]