メニュー
Use when completion gate already allows closeout and the remaining work is state/doc/release-note closure, either for the current completed task or for the whole workflow cycle.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when starting an existing-code bug audit on a repository or large directory tree. First detects project language + architecture (e.g. C/C++ embedded SOA, Python web service, frontend SPA), proposes a tailored review checklist (scenario-specific bug categories) for user confirmation, then slices the codebase into modules within a per-module token budget. Produces plan.json with profile + review_checklist + modules that downstream audit-reviewer consumes module-by-module. Not for PR diff review (use hf-code-review) or for actually finding bugs (use audit-reviewer).
Use as the FINAL stage of the code-audit pipeline. Reads confirmed.json (output of audit-verifier) and renders a self-contained single-file HTML report (always) and optionally an Excel workbook. The HTML contains summary stats by severity/category/module, filterable finding cards with code snippets and audit trails (reviewer + verifier). Not for emitting findings (use audit-reviewer) or verifying findings (use audit-verifier).
Use when scanning an existing-code module for bugs and emitting finding drafts. Reads source files within one module from the plan.json produced by audit-planner, walks files line-by-line, emits findings/<module>.json with file path, line numbers, category, severity, confidence, code snippet evidence, and reasoning. The set of allowed finding categories is sourced from plan.json's review_checklist (scenario preset such as c-cpp-embedded-soa / python-web-service / frontend-spa / generic) rather than a fixed taxonomy — keep findings scoped to the user-confirmed checklist. This is the PRIMARY (first-stage) reviewer in the two-agent confirmation pipeline; downstream audit-verifier independently confirms each finding. Not for PR diff review (use hf-code-review) or for verifying findings (use audit-verifier).
Use as the SECOND-STAGE independent confirmer in the two-agent code-audit pipeline. Reads finding drafts produced by audit-reviewer and independently re-examines each one against the actual source code, writes verifications/<module>.json with status (confirmed/rejected/upgrade/downgrade/needs_more_evidence), reason, and evidence_check. Operates with FRESH context — does not see reviewer's internal reasoning beyond what is recorded in the finding's description+evidence fields, to enable independent judgement. Not for emitting new findings (use audit-reviewer) or rendering the report (use audit-reporter).
Use when hf-test-driven-dev finishes GREEN on a frontend-touching active task whose spec declares a UI surface, and fresh browser runtime evidence (screenshot / console log / network trace) is required for downstream gates. Not for issuing verdicts (gates do that), not for replacing hf-test-review's test-quality review, not for backend-only tasks.
适用于 test review 通过后评审代码质量、用户要求 code review 的场景。不适用于评审测试（→ hf-test-review）、写/修代码（→ hf-test-driven-dev）、阶段不清（→ hf-workflow-router）。
| name | hf-finalize |
| description | Use when completion gate already allows closeout and the remaining work is state/doc/release-note closure, either for the current completed task or for the whole workflow cycle. |
正式做 closeout。这个 skill 有两个合法分支：
task closeout：当前任务已经完成并通过 completion gate，但 workflow 里仍有剩余 approved tasks，需要把状态收口后交回 hf-workflow-routerworkflow closeout：当前任务完成后，已无剩余 approved tasks，需要把整个工作周期正式关闭它不做：新实现、不替代 completion gate、不替代 router 决定下一任务。
本 skill 融合以下已验证方法：
适用：
hf-completion-gate 已给出支持 closeout 的结论不适用：
hf-completion-gatehf-test-driven-dev / 上游 gatehf-workflow-routertask closeout 或 workflow closeouthf-workflow-routerworkflow closeout 在 interactive 模式下必须先给出 closeout summary，再等真人确认后才把 next action 写成 nullcloseout.md 后必须同时产出 closeout.html 视觉伴生报告（除非 closeout.md 自身因前置步骤判定不写入）先只回答一件事：本次是哪个 closeout 分支？
| 条件 | Closeout Type | Next Action |
|---|---|---|
| 当前任务完成，但仍有剩余 approved tasks | task closeout | hf-workflow-router |
| 当前任务完成，且已无剩余 approved tasks | workflow closeout | null / 项目 null 约定 |
| 剩余任务是否存在不清、或 queue 证据冲突 | blocked | hf-workflow-router |
读：
features/<active>/verification/）features/<active>/reviews/、features/<active>/approvals/）features/<active>/tasks.md、features/<active>/task-board.md）progress.md（默认 features/<active>/progress.md，含 worktree 字段）README.md（默认 features/<active>/README.md）docs/release-notes/vX.Y.Z.md + 仓库根 CHANGELOG.md）docs/arc42/、docs/runbooks/、docs/slo/、docs/adr/、docs/index.md）Profile-aware 证据矩阵：
full / standard：需要 closeout 所依赖的 reviews + gates 已落盘lightweight：至少 regression + completion 已落盘在判断 closeout type 前，先确认：
completion / regression 记录已落盘，且与当前 stage / active task / worktree 语义一致N/A（按 profile 跳过）若不满足，不进入 task closeout 或 workflow closeout，而是明确写成 blocked，并把唯一下一步交回 hf-workflow-router。
显式写出：
task closeout / workflow closeout / blocked若无法稳定判断，就停止 finalize，交回 hf-workflow-router。
无论哪种 closeout，都要同步：
分支规则：
task closeout：Current Stage 写回 hf-workflow-router；Next Action 写 hf-workflow-routerworkflow closeout：Current Stage 标记为 closed / completed；Next Action 写 null 或项目 null 约定task closeout 不要求额外人工确认；它只是把当前任务收口后交回 router。
workflow closeout 则不同：它会把整个工作周期收口为 closed / completed，并把 Next Action Or Recommended Skill 写成 null。因此：
interactive：先展示 closeout summary + evidence matrix + worktree disposition，等待真人确认“正式结束本轮 workflow”auto：先写 closeout pack，再按项目 auto 规则把 workflow 视为已关闭如果用户不同意结束 workflow，或希望保留后续动作，则不要写 null，应回到 hf-workflow-router。
docs/，更新 release notes / CHANGELOG遵循 sync-on-presence 原则：同步范围按 docs/ 实际存在的子目录 + 本 feature 触发了升级条件的子目录决定，不要求项目同步未启用的资产。docs/ 各档载体（docs/architecture.md 单文件 vs docs/arc42/ 拆分；docs/runbooks/ / docs/slo/ / docs/postmortems/ / docs/release-notes/ / docs/diagrams/ / docs/insights/ / docs/index.md 等可选子目录；仓库根 CHANGELOG.md / README.md）按存在判断；具体载体清单见下方"必须 / 条件 / N/A"三类列表。
必须同步项（任何 tier）：
docs/adr/NNNN-...md：把状态 proposed 翻为 accepted（设计阶段已落地，此处仅状态翻转 + 必要 supersedes / superseded-by 双向链接）CHANGELOG.md：写入 vX.Y.Z 入口（Keep a Changelog 风格）README.md 中的 active feature / 最近 closeout / ADR 索引行；档 2 更新 docs/index.md按存在同步项（仅当对应载体已启用或本 closeout 触发升级条件）：
docs/architecture.md（档 1）或 docs/arc42/（档 2）—— 同步本 feature 改变的架构图景；二者只能同时存在一份docs/architecture.md 的术语表节；档 2 时落到 docs/arc42/12_glossary.mddocs/runbooks/...：仅当目录已存在或本 feature 引入第一个生产部署运维点docs/slo/...：仅当目录已存在或本 feature 引入第一个 SLOdocs/diagrams/...：仅当目录已存在或本 feature 引入需要源码化的图docs/release-notes/vX.Y.Z.md：仅当目录已启用（档 2）；档 0/1 时仅 CHANGELOG.md 即可并检查规格/设计/任务/状态文档（features/<active>/ 内）是否与 closeout 结论一致。
判 blocked 的条件收紧为：
未启用的可选资产（如档 0/1 项目尚未启用的 docs/runbooks/ / docs/slo/）不构成 blocked 依据，应在 closeout pack 中显式标 N/A（项目当前未启用此资产） 或 N/A（本 feature 未触发该资产变化）。
每条 closeout 证据都写出：
N/A（按 profile 跳过）写入 features/<active>/closeout.md（基于 references/finalize-closeout-pack-template.md）。至少写出：
closeout.md 是 canonical 机器可读契约，但对人类 reviewer 不够直观。Finalize 结束前必须额外产出一份 HTML 工作总结报告，作为 closeout.md 的视觉伴生文件：
features/<active>/closeout.html（与 closeout.md 同目录）skills/hf-finalize/scripts/render-closeout-html.py <feature-dir>（纯 Python stdlib，无外部依赖；脚本随 skill 一起 vendor，OpenCode .opencode/skills/ 软链接 / Cursor .cursor/rules/ 集成路径都能直接拿到）closeout.md + evidence/*.log + verification/*.md + verification/coverage.json（如存在）解析得到，自包含单文件，含嵌入式 CSS / 极小 JS，离线可读执行命令（默认）：
python3 skills/hf-finalize/scripts/render-closeout-html.py features/<active>/
判 blocked 的情况下也要尝试生成（HTML 自身能展示 blocked 徽标 + 缺失证据状态）；只有当 closeout.md 因前置步骤判定不写入时才跳过。
覆盖率取数说明：
verification/coverage.json（istanbul / vitest --coverage --reporter=json-summary 的 total 字段）verification/*.md 与 evidence/*.log 的 Lines: 92.5% / Branches: 70% / istanbul All files | ... 表格行中扫描不在 HTML 里塞新的事实：HTML 报告只是渲染 closeout.md + 已落盘的 evidence，不允许引入 closeout pack 之外的新 conclusion / approval。
默认 closeout pack 结构：
## Closeout Summary
- Closeout Type: `task-closeout` | `workflow-closeout` | `blocked`
- Scope:
- Conclusion:
- Based On Completion Record:
- Based On Regression Record:
## Evidence Matrix
- Artifact:
- Record Path:
- Status:
## State Sync
- Current Stage:
- Current Active Task:
- Workspace Isolation:
- Worktree Path:
- Worktree Branch:
- Worktree Disposition:
## Release / Docs Sync
- Release Notes Path: # 档 0/1：CHANGELOG.md（vX.Y.Z 入口）；档 2：docs/release-notes/vX.Y.Z.md
- CHANGELOG Path: # 例：CHANGELOG.md（v1.5.0 入口）—— 任何 tier 必填
- Updated Long-Term Assets: # 按存在同步：列出本次同步路径，未启用项写 N/A
- docs/adr/NNNN-...md（status: proposed → accepted）
- 架构概述：docs/architecture.md（档 1）或 docs/arc42/...（档 2）；本 feature 未触发架构变化时写 N/A
- docs/runbooks/...：N/A（项目当前未启用此资产）/ N/A（本 feature 未触发）/ 实际路径
- docs/slo/...：同上
- docs/diagrams/...：同上
- Index Updated: # 档 0/1：仓库根 README.md 中 active feature 行；档 2：docs/index.md
## Handoff
- Remaining Approved Tasks:
- Next Action Or Recommended Skill:
- PR / Branch Status:
- Limits / Open Notes:
Closeout type-specific 约束：
task closeout：Next Action Or Recommended Skill 必须是 hf-workflow-routerworkflow closeout：Next Action Or Recommended Skill 必须是 null 或项目 null 约定blocked：Next Action Or Recommended Skill 必须是 hf-workflow-router，且不得声称 closeout 已完成workflow closeout 在 interactive 模式下追加：
## Final Confirmation
- Question: 是否确认正式结束本轮 workflow？
- If confirmed: write `Next Action Or Recommended Skill: null`
- If not confirmed: return to `hf-workflow-router`
| 文件 | 用途 |
|---|---|
references/finalize-closeout-pack-template.md | closeout pack 模板（含 HTML 伴生报告字段说明） |
scripts/render-closeout-html.py（本 skill 子目录 skills/hf-finalize/scripts/，ADR-006 引入的 skill-owned 工具约定） | 由 closeout.md + 旁路工件生成 closeout.html 视觉报告，纯 Python stdlib，自包含单文件输出。仓库根 scripts/ 保留给跨 skill 的维护者工具（如 audit-skill-anatomy.py） |
hf-test-driven-dev/references/worktree-isolation.md | worktree disposition 的收尾语义（不擅自删除；只记录 kept-for-pr / cleaned-per-project-rule / in-place） |
task closeout 和 workflow closeouthf-workflow-routerdocs/runbooks/ / docs/slo/）误判 blockeddocs/architecture.md 与 docs/arc42/（架构概述应二选一）features/archived/，破坏其它工件的反向引用closeout.md 不生成 closeout.html，或在 HTML 里捏造 closeout.md 之外的 conclusion / 测试数据 / 覆盖率| 借口 | 反驳 / Hard rule |
|---|---|
| "completion-gate pass 了，state sync 我下次会话再补。" | Hard Gates: state sync / progress 闭合是 finalize 必需输出；跨会话补 = 没补。 |
| "release notes 我直接复制 commit messages。" | Workflow stop rule: release notes 必须按 PMBOK closeout 的格式，覆盖 scope / artifact / handoff，不是 commit dump。 |
| "handoff pack 不重要，next agent 自己看 commit。" | Hard Gates: handoff pack 是 evidence-based recovery 的唯一入口；缺位 → 下游 agent 无 canonical 起点。 |
| "finalize 之后顺便 deploy。" | Hard Gates (ADR-001 D1 / ADR-002 D1): 主链终点是工程级 closeout；deploy / ship / ops 不在 v0.1.x / v0.2.x 范围。 |
blocked + hf-workflow-routerprogress.md / release notes / CHANGELOG / docs/ 长期资产已按存在同步，closeout pack Release / Docs Sync 区块显式列出实际同步路径与 N/A 项proposed 翻为 accepted（如适用）README.md；档 2 更新 docs/index.mdREADME.md 中 Closed / Closeout Type / Linked Long-Term Assets 等区块已更新docs/slo/ / docs/postmortems/）误判 blockedfeatures/<active>/closeout.mdfeatures/<active>/closeout.html（由 python3 skills/hf-finalize/scripts/render-closeout-html.py <feature-dir> 生成；脚本与 skill 同 vendor）；缺覆盖率数据时 HTML 已显式标注"未提供"，未编造数据task closeout 时 next action = hf-workflow-routerworkflow closeout 时 next action = null 或项目 null 约定workflow closeout 在 interactive 模式下已显式经过最终确认features/，未被移动到 features/archived/