[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7APXE188EM5EJDXAQGD6BZ4":3,"skill-same:01M7APXE188EM5EJDXAQGD6BZ4":52},{"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":30,"commitSha":31,"skillDirectory":32,"forksCount":14,"repositoryHtmlUrl":33,"repositoryHomepageUrl":6,"ownerHtmlUrl":34,"ownerBlogUrl":35,"ownerDescription":36,"updatedAt":37,"install":38,"resources":51},"01M7APXE188EM5EJDXAQGD6BZ4","tdd",null,"Red-Green-Refactor for changes with behavior or regression risk. Use when: adding observable behavior, fixing a bug, or changing logic not already covered by a precise executable check. Not for: pure docs\u002Fresearch, deterministic generated-artifact refreshes, or mechanical changes already covered by an existing checker. Output: observed RED (new test or existing failing check) → minimal GREEN → refactor under protection.","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\u002Ftdd\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: tdd\ndescription: >\n  Red-Green-Refactor for changes with behavior or regression risk.\n  Use when: adding observable behavior, fixing a bug, or changing logic not already covered by a precise executable check.\n  Not for: pure docs\u002Fresearch, deterministic generated-artifact refreshes, or mechanical changes already covered by an existing checker.\n  Output: observed RED (new test or existing failing check) → minimal GREEN → refactor under protection.\ntriggers:\n  - \"写代码\"\n  - \"test first\"\n  - \"TDD\"\n  - \"红绿重构\"\n---\n\n# TDD（测试驱动开发）\n\n行为变化先看到一个可信的失败信号，再写最少实现把它变绿。**RED 是证据状态，不是必须新建测试文件。**\n\n## 风险入口\n\n| 改动 | 怎么走 |\n|---|---|\n| 新增用户可见 \u002F runtime 行为 | 先写能失败的行为测试，再实现 |\n| 修 bug，现有测试没有复现 | 先补回归测试，确认按正确原因失败 |\n| 现有精确检查已经红 | 这就是现成 RED；直接修到该检查绿，不重复造测试 |\n| 确定性生成物过期 | generator \u002F sync check 的失败就是 RED；重生成后复跑，不另写“测试生成物存在”的测试 |\n| 纯文档、调研、无行为的机械改动 | 不触发本 skill；跑与改动面匹配的校验 |\n\n判断标准不是“有没有写代码”，而是“是否引入或修复了可观察行为，且现有检查能否准确保护它”。拿不准是否有行为风险时，按有风险处理。\n\n## RED 来源\n\nRED 可以来自两处：\n\n1. **新测试**：现有检查没有表达目标行为。先写测试，亲眼确认它以预期原因失败。\n2. **现有检查**：CI、typecheck、schema\u002Findex freshness、generator drift 等已经准确指出目标差异。保存命令与失败输出；它已经完成了 RED 的工作。\n\n禁止为了仪式感叠加第二个等价 RED。尤其是 checked-in index、代码生成结果、格式化快照等确定性派生物：精准 checker 红 → 重生成 → 同一 checker 绿，就是完整闭环。\n\n## Red-Green-Refactor\n\n```text\nRED      观察可信失败信号\n  ↓\nGREEN    写最少实现，让同一信号通过；相关检查也保持绿\n  ↓\nREFACTOR 消除重复、改善命名，不新增行为；复跑同一保护集\n```\n\n- RED 立即通过：目标行为已经存在，或检查没覆盖目标；先纠正测试\u002F判断。\n- RED 是语法错误、环境错误：修到它能准确表达行为失败再继续。\n- GREEN 让别的检查变红：停下修复回归，不扩 scope。\n- REFACTOR 后变红：回退这次重构，重新收敛。\n\n## Bug Fix 模式\n\n未知根因、跨层或非确定性 bug 先加载 `debugging`，用[诊断胶囊](..\u002Frefs\u002Fbug-diagnosis-capsule.md)定位；确定根因后再选择 RED：\n\n- 没有现成复现 → 新增失败回归测试；\n- 已有精确失败检查 → 直接把它当 RED；\n- 确定性 `main` 红且修复可逆、无行为变化 → 走 Harness Diet fix-forward，不为找 owner 或新建测试排队。\n\n安全、鉴权、生产数据、外部契约与不可逆面即使已有 RED，也不因此降级其他门禁；RED 只回答测试入口，不回答授权与合入风险。\n\n## 正反灰例\n\n- 正例：API 对空 token 返回 200，现有测试没覆盖 → 先补失败回归测试。\n- 正例：`pnpm check:sop-definitions` 报 checked-in 生成文件 stale → 该失败就是 RED，运行 generator 后复验。\n- 反例：给纯 discussion 改措辞 → 不写单测，跑 docs\u002Fformat 校验。\n- 反例：index generator 已精准报 drift，却另造一个同义单测 → 删除重复测试。\n- 灰例：机械 rename 有完整 typecheck 覆盖 → typecheck 红可作 RED；若还改变对外名字\u002F契约，则升级为行为测试 + 契约风险车道。\n\n## Common Mistakes\n\n| 错误 | 后果 | 修正 |\n|---|---|---|\n| 先实现，再补从未失败过的测试 | 无法证明测试能抓回归 | 回到可观察 RED |\n| 把“测试文件”当 TDD 目标 | 给确定性生成物制造冗余测试 | 复用现有精确检查 |\n| 因为已有 RED 就跳过安全\u002F授权边界 | 测试证据被误当风险许可证 | 风险路由独立判断 |\n| 小修也强造新 RED | 仪式成本高于信息增益 | 无行为或现有 checker 已覆盖就不新增 |\n| RED 只是环境\u002F拼写错误仍继续 | 失败信号不可信 | 修到按预期原因失败 |\n\n## 和其他 skill 的区别\n\n- `debugging`：先定位未知根因；TDD 在方向确定后保护行为变化。\n- `quality-gate`：按风险汇总交付证据；TDD 只负责实现循环中的行为保护。\n\n## 下一步\n\n实现完成后，按风险选择 targeted 自检或 `quality-gate`；不要因使用了 TDD 自动触发其余所有车道。\n","# TDD（测试驱动开发）\n\n行为变化先看到一个可信的失败信号，再写最少实现把它变绿。**RED 是证据状态，不是必须新建测试文件。**\n\n## 风险入口\n\n| 改动 | 怎么走 |\n|---|---|\n| 新增用户可见 \u002F runtime 行为 | 先写能失败的行为测试，再实现 |\n| 修 bug，现有测试没有复现 | 先补回归测试，确认按正确原因失败 |\n| 现有精确检查已经红 | 这就是现成 RED；直接修到该检查绿，不重复造测试 |\n| 确定性生成物过期 | generator \u002F sync check 的失败就是 RED；重生成后复跑，不另写“测试生成物存在”的测试 |\n| 纯文档、调研、无行为的机械改动 | 不触发本 skill；跑与改动面匹配的校验 |\n\n判断标准不是“有没有写代码”，而是“是否引入或修复了可观察行为，且现有检查能否准确保护它”。拿不准是否有行为风险时，按有风险处理。\n\n## RED 来源\n\nRED 可以来自两处：\n\n1. **新测试**：现有检查没有表达目标行为。先写测试，亲眼确认它以预期原因失败。\n2. **现有检查**：CI、typecheck、schema\u002Findex freshness、generator drift 等已经准确指出目标差异。保存命令与失败输出；它已经完成了 RED 的工作。\n\n禁止为了仪式感叠加第二个等价 RED。尤其是 checked-in index、代码生成结果、格式化快照等确定性派生物：精准 checker 红 → 重生成 → 同一 checker 绿，就是完整闭环。\n\n## Red-Green-Refactor\n\n```text\nRED      观察可信失败信号\n  ↓\nGREEN    写最少实现，让同一信号通过；相关检查也保持绿\n  ↓\nREFACTOR 消除重复、改善命名，不新增行为；复跑同一保护集\n```\n\n- RED 立即通过：目标行为已经存在，或检查没覆盖目标；先纠正测试\u002F判断。\n- RED 是语法错误、环境错误：修到它能准确表达行为失败再继续。\n- GREEN 让别的检查变红：停下修复回归，不扩 scope。\n- REFACTOR 后变红：回退这次重构，重新收敛。\n\n## Bug Fix 模式\n\n未知根因、跨层或非确定性 bug 先加载 `debugging`，用[诊断胶囊](..\u002Frefs\u002Fbug-diagnosis-capsule.md)定位；确定根因后再选择 RED：\n\n- 没有现成复现 → 新增失败回归测试；\n- 已有精确失败检查 → 直接把它当 RED；\n- 确定性 `main` 红且修复可逆、无行为变化 → 走 Harness Diet fix-forward，不为找 owner 或新建测试排队。\n\n安全、鉴权、生产数据、外部契约与不可逆面即使已有 RED，也不因此降级其他门禁；RED 只回答测试入口，不回答授权与合入风险。\n\n## 正反灰例\n\n- 正例：API 对空 token 返回 200，现有测试没覆盖 → 先补失败回归测试。\n- 正例：`pnpm check:sop-definitions` 报 checked-in 生成文件 stale → 该失败就是 RED，运行 generator 后复验。\n- 反例：给纯 discussion 改措辞 → 不写单测，跑 docs\u002Fformat 校验。\n- 反例：index generator 已精准报 drift，却另造一个同义单测 → 删除重复测试。\n- 灰例：机械 rename 有完整 typecheck 覆盖 → typecheck 红可作 RED；若还改变对外名字\u002F契约，则升级为行为测试 + 契约风险车道。\n\n## Common Mistakes\n\n| 错误 | 后果 | 修正 |\n|---|---|---|\n| 先实现，再补从未失败过的测试 | 无法证明测试能抓回归 | 回到可观察 RED |\n| 把“测试文件”当 TDD 目标 | 给确定性生成物制造冗余测试 | 复用现有精确检查 |\n| 因为已有 RED 就跳过安全\u002F授权边界 | 测试证据被误当风险许可证 | 风险路由独立判断 |\n| 小修也强造新 RED | 仪式成本高于信息增益 | 无行为或现有 checker 已覆盖就不新增 |\n| RED 只是环境\u002F拼写错误仍继续 | 失败信号不可信 | 修到按预期原因失败 |\n\n## 和其他 skill 的区别\n\n- `debugging`：先定位未知根因；TDD 在方向确定后保护行为变化。\n- `quality-gate`：按风险汇总交付证据；TDD 只负责实现循环中的行为保护。\n\n## 下一步\n\n实现完成后，按风险选择 targeted 自检或 `quality-gate`；不要因使用了 TDD 自动触发其余所有车道。\n",{"name":5,"triggers":24,"description":29},[25,26,27,28],"写代码","test first","TDD","红绿重构","Red-Green-Refactor for changes with behavior or regression risk. Use when: adding observable behavior, fixing a bug, or changing logic not already covered by a precise executable check. Not for: pure docs\u002Fresearch, deterministic generated-artifact refreshes, or mechanical changes already covered by an existing checker. Output: observed RED (new test or existing failing check) → minimal GREEN → refactor under protection.\n","main","e43f83d5ceb309323cae7e0f31e5e48fd816a57d","cat-cafe-skills\u002Ftdd","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":39,"prompt":49,"zipAvailable":50},[40,43,46],{"tool":41,"command":42},"npx","npx skills add peps1666\u002FBuildCrew-AI --skill tdd",{"tool":44,"command":45},"bunx","bunx skills add peps1666\u002FBuildCrew-AI --skill tdd",{"tool":47,"command":48},"pnpm","pnpm dlx skills add peps1666\u002FBuildCrew-AI --skill tdd","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fpeps1666\u002FBuildCrew-AI\u002Fblob\u002Fmain\u002Fcat-cafe-skills\u002Ftdd\u002FSKILL.md",true,[],[53,59,66,73,80,87],{"skillNo":54,"name":55,"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":56,"categories":57,"keywords":58,"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":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"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":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"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":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"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":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"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":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"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",[],[]]