[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D75DTZJEM118WRJPK2V32M":3,"skill-same:01M7D75DTZJEM118WRJPK2V32M":46},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M7D75DTZJEM118WRJPK2V32M","ac-review",null,"AllstarCoding 流水环节 8 的评审环节使用。当需要委派评审子检查任务开发产出、判断 pass\u002Ffail、把评审结果落盘 reviews.md 并对账、把评审结果转达打回、或复核被打回后的修正时加载本技能。含评审维度 checklist 与 verdict 输出规范。","hxquan-q\u002Fopen-forge","hxquan-q","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F180607655?v=4","01M7D70QBFWC9ZVGC49W3Y6J1M","xquan","01M7D70QC45F445W6V1AK76JZ7",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhxquan-q\u002Fopen-forge\u002Fblob\u002Fmain\u002Fpackages\u002Fplugins\u002Fpresets\u002Fallstar-coding\u002Fagent\u002Fskills\u002Fac-review\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: ac-review\ndescription: AllstarCoding 流水环节 8 的评审环节使用。当需要委派评审子检查任务开发产出、判断 pass\u002Ffail、把评审结果落盘 reviews.md 并对账、把评审结果转达打回、或复核被打回后的修正时加载本技能。含评审维度 checklist 与 verdict 输出规范。\n---\n\u003C!-- Copyright The Open Forge contributors. -->\n\n# AC 任务评审（流水环节 8 · 评审侧）\n\n目标：定义**评审子怎么评、verdict 怎么出、评审记录怎么落盘对账、打回怎么走**。评审子 = `spawn_agent` 的 **general 型**、契约 scope 仅 `docs\u002Fac\u002Freviews.md`，每任务一个，不复用、不与开发子共享上下文——独立无偏由「新起会话 + 写域唯一 + V2\u002FV4 双链审计兜底」保障（不再依赖 explorer 机制只读）。\n\n## 1. 委派评审（主控）\n\n1. 开发子 settlement 通知到达 → 从其最终报告取\"已完成\"清单。\n2. spawn_agent（general 型，task_name 如 `review_t1`，契约 scope：`docs\u002Fac\u002Freviews.md`）发起评审，任务书含：\n   - **评审对象**：tasks.md 的 T\u003Cn> 节（任务卡全文）+ 开发子报告的改动清单\n   - **依据**：design.md 相关节路径 + requires.md 验收标准（A#）\n   - **评审维度**：§2 四维\n   - **输出格式**：§3 verdict 规范\n   - **证据要求**：必须实际打开改动文件核对——报告说改了什么不算数，文件里真改了才算。可执行判据（文件存在\u002F命令退出码）实际执行贴输出；执行受限记\"未验证\"而非 pass。\n   - **写域**：评审子的整理规划与评审记录落点是 `docs\u002Fac\u002Freviews.md`（追加制，ac-pipeline §0.4）——不是 review-log.md（旧名弃用），更不是其他 docs\u002Fac\u002F 文件。verdict 由评审子**自行落盘**，主控只对账（G4：最新节 verdict == 口头回报），不代写。\n3. 复评（打回后）：**新起评审子**，任务书附上轮问题清单，要求逐条对状态（已修\u002F未修\u002F新引入）。首个评审附：tasks.md 对 design.md 改动面\u002F「必须同步」项的覆盖性复核（ac-taskplan §6.4 清单）。\n\n## 2. 评审维度（四维 + 硬检查，逐项过）\n\n| 维度 | 检查什么 | 证据 |\n|------|----------|------|\n| 0 产物完备性（硬检查） | requires\u002Fdesign\u002Ftasks 三文档存在且非空 | 命令输出贴报告（每次必跑） |\n| 1 调用链完整性 | 新代码上下游接全：入口\u002F出口\u002F调用方\u002F被调方\u002F注册点\u002F配置引用 | grep 调用点逐个在位；删除\u002F重命名符号全仓无残留引用 |\n| 2 业务逻辑正确性 | 实现符合需求与开发文档；边界\u002F空值\u002F错误路径处理 | 对照 requires 验收标准 + design 语义；平台差异（Windows） |\n| 3 结构破坏 | 未越任务卡范围；未破坏既有结构（无关文件、签名变化未同步、删除在用物） | git diff 范围核对 + design\"必须同步\"清单逐项 |\n| 4 验收标准差距 | 任务卡验收条目逐条核对（可执行判据实际执行） | 每条给出 通过\u002F差距\u002F未验证 |\n\n证据规则：每个 fail 结论必须带 文件:位置；\"感觉有问题\"不算，要\"看到 X 处 Y 与 Z 不符\"。\n\n## 3. verdict 规范（评审子输出格式，写进任务书）\n\n```\nverdict: pass | fail\n问题清单:（fail 时必填）\n- [严重] \u003C文件:位置> \u003C问题> → \u003C修正建议>\n- [一般] ……\n- [轻微] ……\n逐维度小结: 5 行，每维一句\n复评说明（若为复评）: 上轮问题逐条状态（已修\u002F未修\u002F新引入）\n```\n\n判定规则：\n- **任一 [严重] 未解决 → fail**。[严重] = 调用链断、逻辑错误、结构破坏、验收条目不达标。\n- [一般] 存在但无 [严重] → 可 pass，问题清单原样转开发子（下一任务顺带修或记 reviews.md）。\n- [轻微] → pass，记录即可。\n- **意见不确定时倾向 fail**：宁可多一轮打回，不放过带病任务（但打回理由必须可验证，不猜）。\n\n## 4. 打回流程（主控执行）\n\n1. verdict=fail → 完整问题清单通过 `followup_task(dev_t\u003Cn>, ...)` 转达同一开发子会话，格式：问题清单 + \"逐条修复后回报，不要求解释，要求修复或说明为何不能修\"。\n2. 开发子修正 settlement → 新起评审子复评（附上轮问题清单）。\n3. 计数：同一 T 打回轮次 ≥1 记 reviews.md 与 state.md（executions+1）；上限 3 轮（ac-pipeline §0）——达上限仍 fail 停止，把分歧（评审意见 vs 开发者回应）整理上报用户裁决。\n4. verdict=pass → reviews.md 记录该 T 通过（含遗留 [一般]\u002F[轻微] 项），state.md 更新（subStep done、sessionStatus suspended），T 档存档（ac-dev §4.5），进下一 T。\n\n## 5. reviews.md 评审记录规范（追加制，ac-pipeline §0.4）\n\n评审子写域落地为轻量节格式（防写飞的最小约束）：\n\n```markdown\n## T\u003Cn> · 第 \u003C轮> 评审\nverdict: pass | fail\n问题清单:（fail 必填；[严重\u002F一般\u002F轻微] 文件:位置 问题 → 建议）\n证据:（静态判据引用 file:line；命令判据引用主控预跑输出）\n```\n\n- **追加不清空**：天然形成评审史；`\u003CT编号, 轮次>` 双键与 state.md 的 executions 计数严格对账；复评任务书直接引用上节原文。\n- **verdict 对账钩子**：主控收口时核对「reviews.md 最新节 verdict == 评审子口头回报 verdict」——不一致以落盘为准，按越权处置 SOP 记录（ac-pipeline §0.6）。\n- 每轮一行摘要可另记表格（历史兼容格式）：\n\n```markdown\n## T\u003Cn> 评审记录\n| 轮次 | verdict | 严重\u002F一般\u002F轻微 | 摘要 |\n|------|---------|----------------|------|\n| 1 | fail | 2\u002F1\u002F0 | 调用链缺注册；已打回 dev_t1 |\n| 2 | pass | 0\u002F1\u002F0 | 修复确认；遗留 1 一般项记入待办 |\n```\n\n## 6. 边界\n\n- 评审子只评不改：写域仅 `docs\u002Fac\u002Freviews.md`（自留地）；问题经主控转达，不直接给开发子留言。写其他任何文件 = 越权，V2 双链校验会抓（mtime 链抓「改了没提交的」）。\n- 评审对象是**当前 T 的改动**；上轮遗留 [一般] 项的修复情况在复评说明里带一句。\n- 评审子自身出错（工具被拒\u002F超时）→ 主控重起评审子，不计打回轮次。\n","\u003C!-- Copyright The Open Forge contributors. -->\n\n# AC 任务评审（流水环节 8 · 评审侧）\n\n目标：定义**评审子怎么评、verdict 怎么出、评审记录怎么落盘对账、打回怎么走**。评审子 = `spawn_agent` 的 **general 型**、契约 scope 仅 `docs\u002Fac\u002Freviews.md`，每任务一个，不复用、不与开发子共享上下文——独立无偏由「新起会话 + 写域唯一 + V2\u002FV4 双链审计兜底」保障（不再依赖 explorer 机制只读）。\n\n## 1. 委派评审（主控）\n\n1. 开发子 settlement 通知到达 → 从其最终报告取\"已完成\"清单。\n2. spawn_agent（general 型，task_name 如 `review_t1`，契约 scope：`docs\u002Fac\u002Freviews.md`）发起评审，任务书含：\n   - **评审对象**：tasks.md 的 T\u003Cn> 节（任务卡全文）+ 开发子报告的改动清单\n   - **依据**：design.md 相关节路径 + requires.md 验收标准（A#）\n   - **评审维度**：§2 四维\n   - **输出格式**：§3 verdict 规范\n   - **证据要求**：必须实际打开改动文件核对——报告说改了什么不算数，文件里真改了才算。可执行判据（文件存在\u002F命令退出码）实际执行贴输出；执行受限记\"未验证\"而非 pass。\n   - **写域**：评审子的整理规划与评审记录落点是 `docs\u002Fac\u002Freviews.md`（追加制，ac-pipeline §0.4）——不是 review-log.md（旧名弃用），更不是其他 docs\u002Fac\u002F 文件。verdict 由评审子**自行落盘**，主控只对账（G4：最新节 verdict == 口头回报），不代写。\n3. 复评（打回后）：**新起评审子**，任务书附上轮问题清单，要求逐条对状态（已修\u002F未修\u002F新引入）。首个评审附：tasks.md 对 design.md 改动面\u002F「必须同步」项的覆盖性复核（ac-taskplan §6.4 清单）。\n\n## 2. 评审维度（四维 + 硬检查，逐项过）\n\n| 维度 | 检查什么 | 证据 |\n|------|----------|------|\n| 0 产物完备性（硬检查） | requires\u002Fdesign\u002Ftasks 三文档存在且非空 | 命令输出贴报告（每次必跑） |\n| 1 调用链完整性 | 新代码上下游接全：入口\u002F出口\u002F调用方\u002F被调方\u002F注册点\u002F配置引用 | grep 调用点逐个在位；删除\u002F重命名符号全仓无残留引用 |\n| 2 业务逻辑正确性 | 实现符合需求与开发文档；边界\u002F空值\u002F错误路径处理 | 对照 requires 验收标准 + design 语义；平台差异（Windows） |\n| 3 结构破坏 | 未越任务卡范围；未破坏既有结构（无关文件、签名变化未同步、删除在用物） | git diff 范围核对 + design\"必须同步\"清单逐项 |\n| 4 验收标准差距 | 任务卡验收条目逐条核对（可执行判据实际执行） | 每条给出 通过\u002F差距\u002F未验证 |\n\n证据规则：每个 fail 结论必须带 文件:位置；\"感觉有问题\"不算，要\"看到 X 处 Y 与 Z 不符\"。\n\n## 3. verdict 规范（评审子输出格式，写进任务书）\n\n```\nverdict: pass | fail\n问题清单:（fail 时必填）\n- [严重] \u003C文件:位置> \u003C问题> → \u003C修正建议>\n- [一般] ……\n- [轻微] ……\n逐维度小结: 5 行，每维一句\n复评说明（若为复评）: 上轮问题逐条状态（已修\u002F未修\u002F新引入）\n```\n\n判定规则：\n- **任一 [严重] 未解决 → fail**。[严重] = 调用链断、逻辑错误、结构破坏、验收条目不达标。\n- [一般] 存在但无 [严重] → 可 pass，问题清单原样转开发子（下一任务顺带修或记 reviews.md）。\n- [轻微] → pass，记录即可。\n- **意见不确定时倾向 fail**：宁可多一轮打回，不放过带病任务（但打回理由必须可验证，不猜）。\n\n## 4. 打回流程（主控执行）\n\n1. verdict=fail → 完整问题清单通过 `followup_task(dev_t\u003Cn>, ...)` 转达同一开发子会话，格式：问题清单 + \"逐条修复后回报，不要求解释，要求修复或说明为何不能修\"。\n2. 开发子修正 settlement → 新起评审子复评（附上轮问题清单）。\n3. 计数：同一 T 打回轮次 ≥1 记 reviews.md 与 state.md（executions+1）；上限 3 轮（ac-pipeline §0）——达上限仍 fail 停止，把分歧（评审意见 vs 开发者回应）整理上报用户裁决。\n4. verdict=pass → reviews.md 记录该 T 通过（含遗留 [一般]\u002F[轻微] 项），state.md 更新（subStep done、sessionStatus suspended），T 档存档（ac-dev §4.5），进下一 T。\n\n## 5. reviews.md 评审记录规范（追加制，ac-pipeline §0.4）\n\n评审子写域落地为轻量节格式（防写飞的最小约束）：\n\n```markdown\n## T\u003Cn> · 第 \u003C轮> 评审\nverdict: pass | fail\n问题清单:（fail 必填；[严重\u002F一般\u002F轻微] 文件:位置 问题 → 建议）\n证据:（静态判据引用 file:line；命令判据引用主控预跑输出）\n```\n\n- **追加不清空**：天然形成评审史；`\u003CT编号, 轮次>` 双键与 state.md 的 executions 计数严格对账；复评任务书直接引用上节原文。\n- **verdict 对账钩子**：主控收口时核对「reviews.md 最新节 verdict == 评审子口头回报 verdict」——不一致以落盘为准，按越权处置 SOP 记录（ac-pipeline §0.6）。\n- 每轮一行摘要可另记表格（历史兼容格式）：\n\n```markdown\n## T\u003Cn> 评审记录\n| 轮次 | verdict | 严重\u002F一般\u002F轻微 | 摘要 |\n|------|---------|----------------|------|\n| 1 | fail | 2\u002F1\u002F0 | 调用链缺注册；已打回 dev_t1 |\n| 2 | pass | 0\u002F1\u002F0 | 修复确认；遗留 1 一般项记入待办 |\n```\n\n## 6. 边界\n\n- 评审子只评不改：写域仅 `docs\u002Fac\u002Freviews.md`（自留地）；问题经主控转达，不直接给开发子留言。写其他任何文件 = 越权，V2 双链校验会抓（mtime 链抓「改了没提交的」）。\n- 评审对象是**当前 T 的改动**；上轮遗留 [一般] 项的修复情况在复评说明里带一句。\n- 评审子自身出错（工具被拒\u002F超时）→ 主控重起评审子，不计打回轮次。\n",{"name":5,"description":7},"main","5b8347d653ab3cc1323c53dbeddd4c009b330d96","packages\u002Fplugins\u002Fpresets\u002Fallstar-coding\u002Fagent\u002Fskills\u002Fac-review",0,"https:\u002F\u002Fgithub.com\u002Fhxquan-q\u002Fopen-forge","https:\u002F\u002Fwww.openvetta.com","https:\u002F\u002Fgithub.com\u002Fhxquan-q","2026-11-13 17:08:23",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add hxquan-q\u002Fopen-forge --skill ac-review",{"tool":38,"command":39},"bunx","bunx skills add hxquan-q\u002Fopen-forge --skill ac-review",{"tool":41,"command":42},"pnpm","pnpm dlx skills add hxquan-q\u002Fopen-forge --skill ac-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhxquan-q\u002Fopen-forge\u002Fblob\u002Fmain\u002Fpackages\u002Fplugins\u002Fpresets\u002Fallstar-coding\u002Fagent\u002Fskills\u002Fac-review\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M7D79WJRKSSY9DXVHJ8VXS2G","review-canvas","Present a multi-file code review as a Canvas diff artifact. Use when the user asks for a review, 代码评审, 变更审查, or a cross-file summary of changes — not for a single edit (the chat diff card already shows it) or a prose report (report-canvas).","https:\u002F\u002Fgithub.com\u002Fhxquan-q\u002Fopen-forge\u002Fblob\u002Fmain\u002Fpackages\u002Fskill-presets\u002Freview-canvas\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7D79QD1TTMEJSC0XQN8ADSJ","report-canvas","Produce a standalone report, audit board, or long-form analysis as a Canvas artifact. Use when the user asks for a report, 报告, 审计看板, or a deliverable that should live beside chat — not when they only want a short chat answer or to inspect a live web page.","https:\u002F\u002Fgithub.com\u002Fhxquan-q\u002Fopen-forge\u002Fblob\u002Fmain\u002Fpackages\u002Fskill-presets\u002Freport-canvas\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7D79JZ390ZN0950BFNQGE6J","publish-ability","Publish a skill, scene, MCP server, plugin, or bundle to the Vetta ability marketplace. Use when the user asks to upload\u002Fpublish\u002Fsubmit an ability, put a plugin on the marketplace, share a skill with other users, or migrate an existing package into Vetta.","https:\u002F\u002Fgithub.com\u002Fhxquan-q\u002Fopen-forge\u002Fblob\u002Fmain\u002Fpackages\u002Fskill-presets\u002Fpublish-ability\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7D79DP3TX2CCZBT0W8CTZKT","install-ability","在本机 Vetta 中安装能力——插件（plugin）、Skill\u002F场景（scene）与 MCP 服务器。用户说「装一个插件 \u002F install plugin \u002F 从能力市场安装 \u002F 加一个 MCP server \u002F 配置 MCP \u002F 装个 skill」，或插件装完没生效、需要 reload、pending 版本没应用时使用。不用于安装 npm 依赖、IDE 插件、浏览器扩展，也不用于开发插件（那是 plugin-workbench）或创作 Skill（那是 create-skill）。","https:\u002F\u002Fgithub.com\u002Fhxquan-q\u002Fopen-forge\u002Fblob\u002Fmain\u002Fpackages\u002Fskill-presets\u002Finstall-ability\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7D799QHEKZBTFA47YXAWFJS","database-analysis","Answer business questions from connected databases with read-only queries, then analyze metrics, trends, rankings, breakdowns, and period comparisons. Use for 问数、查数、数据库分析、销量\u002F收入\u002F用户指标、同比环比 or follow-up data questions. Not for application database migrations or modifying records.","https:\u002F\u002Fgithub.com\u002Fhxquan-q\u002Fopen-forge\u002Fblob\u002Fmain\u002Fpackages\u002Fskill-presets\u002Fdatabase-analysis\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7D795QA8HPGGC6NJ6J5EEJC","create-skill","Create or update Vetta-compatible Agent Skills. Use when the user asks to create a skill, add a SKILL.md workflow, register a skill in skills-manifest.json, package a skill in a Vetta plugin, or add a built-in Vetta skill preset.","https:\u002F\u002Fgithub.com\u002Fhxquan-q\u002Fopen-forge\u002Fblob\u002Fmain\u002Fpackages\u002Fskill-presets\u002Fcreate-skill\u002FSKILL.md",[],[]]