@fitlab-ai/agent-infra 0.7.6 → 0.8.0

package/templates/.agents/skills/complete-task/SKILL.zh-CN.md

@@ -1,6 +1,8 @@
 ---
 name: complete-task
-description: "标记任务完成并归档"
+description: >
+  标记任务完成并归档。
+  当任务工作已完成并验证、需要收尾归档时使用。
 ---
 
 # 完成任务
@@ -127,6 +129,7 @@ date "+%Y-%m-%d %H:%M:%S%:z"
 - `status`：completed
 - `current_step`：completed
 - `completed_at`：{当前时间戳}
+- `target_date`：仅当为空时写入 `completed_at` 的日期部分（`YYYY-MM-DD`）；已有值（人工填写）则保留
 - `updated_at`：{当前时间戳}
 - `agent_infra_version`：按 `.agents/rules/version-stamp.md` 取值
 - 新增或更新 `## 状态核对` 段，粘贴第 0 步审计命令原文（含 `$ ` 前缀行），放在 `## 活动日志` 之前

package/templates/.agents/skills/complete-task/config/verify.en.json

@@ -15,7 +15,8 @@
         "completed_at"
       ],
       "expected_status": "completed",
-      "require_completed_at": true
+      "require_completed_at": true,
+      "require_target_date": true
     },
     "activity-log": {
       "expected_action_pattern": "(Complete Task|Completed)",

package/templates/.agents/skills/complete-task/config/verify.zh-CN.json

@@ -15,7 +15,8 @@
         "completed_at"
       ],
       "expected_status": "completed",
-      "require_completed_at": true
+      "require_completed_at": true,
+      "require_target_date": true
     },
     "activity-log": {
       "expected_action_pattern": "(Complete Task|Completed)",

package/templates/.agents/skills/create-pr/SKILL.en.md

@@ -1,6 +1,8 @@
 ---
 name: create-pr
-description: "Create a Pull Request to a target branch"
+description: >
+  Create a Pull Request to a target branch.
+  Use when changes are committed and you need to open a Pull Request for review.
 ---
 
 # Create Pull Request

package/templates/.agents/skills/create-pr/SKILL.zh-CN.md

@@ -1,6 +1,8 @@
 ---
 name: create-pr
-description: "创建 Pull Request 到目标分支"
+description: >
+  创建 Pull Request 到目标分支。
+  当变更已提交、需要发起 Pull Request 评审时使用。
 ---
 
 # 创建 Pull Request

package/templates/.agents/skills/create-release-note/SKILL.en.md

@@ -1,6 +1,8 @@
 ---
 name: create-release-note
-description: "Generate release notes from PRs and commits"
+description: >
+  Generate release notes from PRs and commits.
+  Use when preparing a release and you need notes compiled from PRs and commits.
 ---
 
 # Create Release Notes

package/templates/.agents/skills/create-release-note/SKILL.zh-CN.md

@@ -1,6 +1,8 @@
 ---
 name: create-release-note
-description: "从 PR 和 commit 生成版本发布说明"
+description: >
+  从 PR 和 commit 生成版本发布说明。
+  当准备发版、需要从 PR 与 commit 汇总发布说明时使用。
 ---
 
 # 创建发布说明

package/templates/.agents/skills/create-task/SKILL.en.md

@@ -1,6 +1,8 @@
 ---
 name: create-task
-description: "Create a task from a natural-language description"
+description: >
+  Create a task from a natural-language description.
+  Use when you want to turn a free-form idea or request into a tracked task.
 ---
 
 # Create Task
@@ -92,7 +94,6 @@ status: active
 created_at: {YYYY-MM-DD HH:mm:ss±HH:MM}
 updated_at: {YYYY-MM-DD HH:mm:ss±HH:MM}
 agent_infra_version: {agent_infra_version}
-created_by: human
 priority:                  # required; inferred by the AI from the title/description; Urgent | High | Medium | Low
 effort:                    # required; inferred by the AI from the title/description; High | Medium | Low
 start_date:                # optional; YYYY-MM-DD
@@ -101,8 +102,7 @@ current_step: requirement-analysis
 assigned_to: {current AI agent}
 ```
 
-Note: `created_by` is `human` because the task comes from the user's description.
-priority / effort are required: the AI infers them from the task title and description (candidates in `.agents/rules/issue-fields.md`; normalize localized input). Leave start_date / target_date empty at creation - analyze-task / plan-task fill them later; do not invent dates.
+priority / effort are required: the AI infers them from the task title and description (candidates in `.agents/rules/issue-fields.md`; normalize localized input). Leave start_date / target_date empty at creation: `start_date` is written by the analyze stage and `target_date` by the complete stage; do not invent dates.
 
 ### 3. Update Task Status
 

package/templates/.agents/skills/create-task/SKILL.zh-CN.md

@@ -1,6 +1,8 @@
 ---
 name: create-task
-description: "根据自然语言描述创建任务"
+description: >
+  根据自然语言描述创建任务。
+  当想把一段自然语言的想法或需求落为受跟踪的任务时使用。
 ---
 
 # 创建任务
@@ -91,7 +93,6 @@ status: active
 created_at: {YYYY-MM-DD HH:mm:ss±HH:MM}
 updated_at: {YYYY-MM-DD HH:mm:ss±HH:MM}
 agent_infra_version: {agent_infra_version}
-created_by: human
 priority:                  # 必填；由 AI 从标题/描述推断；Urgent | High | Medium | Low
 effort:                    # 必填；由 AI 从标题/描述推断；High | Medium | Low
 start_date:                # 可选；YYYY-MM-DD
@@ -100,8 +101,7 @@ current_step: requirement-analysis
 assigned_to: {当前 AI 代理}
 ```
 
-注意：`created_by` 为 `human`，因为任务来源于用户的描述。
-priority / effort 必填：由 AI 从任务标题与描述推断后填入（候选值见 `.agents/rules/issue-fields.md`；中文输入按本地化映射规范化）。start_date / target_date 创建时保持留空，由 analyze-task / plan-task 阶段填入；不要臆测日期。
+priority / effort 必填：由 AI 从任务标题与描述推断后填入（候选值见 `.agents/rules/issue-fields.md`；中文输入按本地化映射规范化）。start_date / target_date 创建时保持留空：`start_date` 由 analyze 阶段写入、`target_date` 由 complete 阶段写入；不要臆测日期。
 
 ### 3. 更新任务状态
 

package/templates/.agents/skills/import-codescan/SKILL.en.md

@@ -1,6 +1,8 @@
 ---
 name: import-codescan
-description: "Import a Code Scanning alert and create a remediation task"
+description: >
+  Import a Code Scanning alert and create a remediation task.
+  Use when a Code Scanning alert needs to become a tracked remediation task.
 ---
 
 # Import Code Scanning Alert
@@ -52,9 +54,6 @@ Task metadata:
 ```yaml
 id: TASK-{yyyyMMdd-HHmmss}
 codescan_alert_number: <alert-number>
-severity: <critical/high/medium/low>
-rule_id: <rule-id>
-tool: <tool-name>
 ```
 
 ### 3. Update Task Status

package/templates/.agents/skills/import-codescan/SKILL.zh-CN.md

@@ -1,6 +1,8 @@
 ---
 name: import-codescan
-description: "导入 Code Scanning 告警并创建修复任务"
+description: >
+  导入 Code Scanning 告警并创建修复任务。
+  当某条 Code Scanning 告警需要转为受跟踪的修复任务时使用。
 ---
 
 # 导入 Code Scanning 告警
@@ -52,9 +54,6 @@ description: "导入 Code Scanning 告警并创建修复任务"
 ```yaml
 id: TASK-{yyyyMMdd-HHmmss}
 codescan_alert_number: <alert-number>
-severity: <critical/high/medium/low>
-rule_id: <rule-id>
-tool: <tool-name>
 ```
 
 ### 3. 更新任务状态

package/templates/.agents/skills/import-dependabot/SKILL.en.md

@@ -1,6 +1,8 @@
 ---
 name: import-dependabot
-description: "Import a Dependabot alert and create a remediation task"
+description: >
+  Import a Dependabot alert and create a remediation task.
+  Use when a Dependabot alert needs to become a tracked remediation task.
 ---
 
 # Import Dependabot Security Alert
@@ -53,7 +55,6 @@ Task metadata must include:
 ```yaml
 id: TASK-{yyyyMMdd-HHmmss}
 security_alert_number: <alert-number>
-severity: <critical/high/medium/low>
 cve_id: <CVE-ID>
 ghsa_id: <GHSA-ID>
 ```

package/templates/.agents/skills/import-dependabot/SKILL.zh-CN.md

@@ -1,6 +1,8 @@
 ---
 name: import-dependabot
-description: "导入 Dependabot 安全告警并创建修复任务"
+description: >
+  导入 Dependabot 安全告警并创建修复任务。
+  当某条 Dependabot 安全告警需要转为受跟踪的修复任务时使用。
 ---
 
 # 导入 Dependabot 安全告警
@@ -53,7 +55,6 @@ description: "导入 Dependabot 安全告警并创建修复任务"
 ```yaml
 id: TASK-{yyyyMMdd-HHmmss}
 security_alert_number: <alert-number>
-severity: <critical/high/medium/low>
 cve_id: <CVE-ID>
 ghsa_id: <GHSA-ID>
 ```

package/templates/.agents/skills/import-issue/SKILL.en.md

@@ -1,6 +1,8 @@
 ---
 name: import-issue
-description: "Import an Issue and create a task"
+description: >
+  Import an Issue and create a task.
+  Use when you want to start work from an existing Issue and track it locally.
 ---
 
 # Import Issue
@@ -40,7 +42,22 @@ This skill **creates** task.md, so there is no file to write at the start. Captu
 Read `.agents/rules/issue-pr-commands.md` first, follow its prerequisite steps to complete authentication and code-hosting platform detection, then load the Issue data with its "Read an Issue" command.
 
 Extract: issue number, title, description, and labels.
-Use the Issue title as-is for the task title (preserve the Issue's original language).
+
+Derive the task title from the Issue title by stripping an optional single leading Conventional Commits prefix, following the contract below; preserve the rest of the description verbatim and in its original language. This fenced contract is the authoritative, language-neutral rule — keep it byte-for-byte identical across every `import-issue` variant:
+
+```
+# title-derivation-contract
+strip-prefix: type(scope):
+prefix-types: feat fix docs style refactor perf test build ci chore revert
+single-layer-only: true
+preserve-body-colon: true
+keep-when-no-prefix: true
+example-strip: "feat(meta): create-pr summary" => "create-pr summary"
+example-keep: "修复某问题" => "修复某问题"
+example-single-layer: "feat: add A: B" => "add A: B"
+```
+
+Strip only the first layer, and only when the leading token is a `prefix-types` value optionally followed by `(scope)` and a `!`, then `:` and at least one space; a colon inside the description is never a prefix.
 
 ### 2. Check for an Existing Task
 
@@ -76,7 +93,7 @@ date +%Y%m%d-%H%M%S
 
 - Create the directory: `.agents/workspace/active/{task-id}/`
 - Use the `.agents/templates/task.md` template to create `task.md`
-- For Scenario C, prefer `type`, `workflow`, `branch`, `created_by`, and `milestone` from the remote frontmatter; infer missing or damaged fields from Issue labels and current rules
+- For Scenario C, prefer `type`, `workflow`, `branch`, and `milestone` from the remote frontmatter; infer missing or damaged fields from Issue labels and current rules
 - Always write `current_step` as `requirement-analysis`; do not restore the remote original `current_step`
 
 Task metadata:
@@ -90,7 +107,6 @@ status: active
 created_at: {YYYY-MM-DD HH:mm:ss±HH:MM}
 updated_at: {YYYY-MM-DD HH:mm:ss±HH:MM}
 agent_infra_version: {agent_infra_version}
-created_by: human
 priority:                  # optional; preserve source/frontmatter value when available
 effort:                    # optional; preserve source/frontmatter value when available
 start_date:                # optional; preserve explicit YYYY-MM-DD when available

package/templates/.agents/skills/import-issue/SKILL.zh-CN.md

@@ -1,6 +1,8 @@
 ---
 name: import-issue
-description: "从 Issue 导入并创建任务"
+description: >
+  从 Issue 导入并创建任务。
+  当想从既有 Issue 开工并在本地跟踪时使用。
 ---
 
 # 导入 Issue
@@ -40,7 +42,22 @@ description: "从 Issue 导入并创建任务"
 执行前先读取 `.agents/rules/issue-pr-commands.md`，并按其中的前置步骤完成认证和代码托管平台检测；随后按其中的 “读取 Issue” 命令获取 Issue 信息。
 
 提取：issue 编号、标题、描述、标签。
-任务标题直接使用 Issue 的原始标题（保持 Issue 标题的原始语言）。
+
+从 Issue 标题派生任务标题：按下方契约剥掉可选的单层前导 Conventional Commits 前缀，其余描述原文与原始语言保持不变。下方 fenced 契约是权威的、与语言无关的规则——在所有 `import-issue` 变体中保持逐字节一致：
+
+```
+# title-derivation-contract
+strip-prefix: type(scope):
+prefix-types: feat fix docs style refactor perf test build ci chore revert
+single-layer-only: true
+preserve-body-colon: true
+keep-when-no-prefix: true
+example-strip: "feat(meta): create-pr summary" => "create-pr summary"
+example-keep: "修复某问题" => "修复某问题"
+example-single-layer: "feat: add A: B" => "add A: B"
+```
+
+只剥第一层前缀，且仅当前导 token 是 `prefix-types` 之一、其后可带 `(scope)` 与 `!`，再接 `:` 和至少一个空格；描述正文中的冒号永远不算前缀。
 
 ### 2. 检查已有任务
 
@@ -76,7 +93,7 @@ date +%Y%m%d-%H%M%S
 
 - 创建目录：`.agents/workspace/active/{task-id}/`
 - 使用 `.agents/templates/task.md` 模板创建 `task.md`
-- 场景 C 优先沿用远端 frontmatter 中的 `type`、`workflow`、`branch`、`created_by`、`milestone`；缺失或损坏字段按 Issue 标签和当前规则重新推断
+- 场景 C 优先沿用远端 frontmatter 中的 `type`、`workflow`、`branch`、`milestone`；缺失或损坏字段按 Issue 标签和当前规则重新推断
 - `current_step` 始终写入 `requirement-analysis`，不要恢复为远端原 `current_step`
 
 任务元数据：
@@ -90,7 +107,6 @@ status: active
 created_at: {YYYY-MM-DD HH:mm:ss±HH:MM}
 updated_at: {YYYY-MM-DD HH:mm:ss±HH:MM}
 agent_infra_version: {agent_infra_version}
-created_by: human
 priority:                  # 可选；有来源/frontmatter 值时保留
 effort:                    # 可选；有来源/frontmatter 值时保留
 start_date:                # 可选；有明确 YYYY-MM-DD 时保留

package/templates/.agents/skills/init-labels/SKILL.en.md

@@ -1,6 +1,8 @@
 ---
 name: init-labels
-description: "Initialize the repository's standard labels taxonomy"
+description: >
+  Initialize the repository's standard labels taxonomy.
+  Use when setting up a repository and you need the standard label taxonomy created.
 ---
 
 # Initialize labels

package/templates/.agents/skills/init-labels/SKILL.zh-CN.md

@@ -1,6 +1,8 @@
 ---
 name: init-labels
-description: "初始化仓库的 labels 体系"
+description: >
+  初始化仓库的 labels 体系。
+  当初始化仓库、需要创建标准 label 体系时使用。
 ---
 
 # 初始化 labels

package/templates/.agents/skills/init-milestones/SKILL.en.md

@@ -1,6 +1,8 @@
 ---
 name: init-milestones
-description: "Initialize the repository's standard milestones taxonomy"
+description: >
+  Initialize the repository's standard milestones taxonomy.
+  Use when setting up a repository and you need the standard milestone taxonomy created.
 ---
 
 # Initialize milestones

package/templates/.agents/skills/init-milestones/SKILL.zh-CN.md

@@ -1,6 +1,8 @@
 ---
 name: init-milestones
-description: "初始化仓库的 milestones 体系"
+description: >
+  初始化仓库的 milestones 体系。
+  当初始化仓库、需要创建标准 milestone 体系时使用。
 ---
 
 # 初始化 milestones

package/templates/.agents/skills/plan-task/SKILL.en.md

@@ -1,6 +1,8 @@
 ---
 name: plan-task
-description: "Design a technical plan for a task"
+description: >
+  Design a technical plan for a task.
+  Use when a requirement is understood and you need a technical design before coding.
 ---
 
 # Design Technical Plan
@@ -97,7 +99,7 @@ Follow the `technical-design` step in `.agents/workflows/feature-development.yam
 - [ ] Define the verification strategy (tests, manual checks)
 - [ ] Assess impact and risks
 
-When this round introduces a new key design decision, record it under `## Open Questions` according to `.agents/rules/no-mid-flow-questions.md` and write the matching `HD-` ledger row.
+When this round introduces a new key design decision, per `.agents/rules/no-mid-flow-questions.md` write its detail block (background/options/impact/recommendation) into the plan artifact's `## 人工裁决待办` (Pending Human Decisions) section as `### HD-N：<title> [needs-human-decision]` (`HD-N` is globally unique, see `.agents/rules/review-handshake.md`), and write the matching `HD-` ledger row (evidence pointing to `{plan-artifact}#HD-N`); ordinary open questions still go under `## Open Questions`.
 
 **Design principles**:
 1. **Architectural soundness**: choose the structurally correct approach; diff size is not the primary criterion. Do not pile changes onto an unsound structure just to keep the diff small
@@ -123,7 +125,6 @@ Update `.agents/workspace/active/{task-id}/task.md`:
 - `assigned_to`: {current AI agent}
 - `updated_at`: {current time}
 - `agent_infra_version`: value from `.agents/rules/version-stamp.md`
-- If `target_date` is empty, write an estimated completion date based on the effort estimate (`YYYY-MM-DD`); leave it empty without blocking when no reasonable estimate exists; keep any existing value
 - Record the plan artifact for this round: `{plan-artifact}` (Round `{plan-round}`)
 - If the task template contains a `## Design` section, update it to link to `{plan-artifact}`
 - Mark technical-design as complete in workflow progress and include the actual round when the task template supports it

package/templates/.agents/skills/plan-task/SKILL.zh-CN.md

@@ -1,6 +1,8 @@
 ---
 name: plan-task
-description: "为任务设计技术方案和实施计划"
+description: >
+  为任务设计技术方案和实施计划。
+  当需求已明确、需要在编码前形成技术方案时使用。
 ---
 
 # 设计技术方案
@@ -96,7 +98,7 @@ tail .agents/workspace/active/{task-id}/task.md
 - [ ] 定义验证策略（测试、手动检查）
 - [ ] 评估方案的影响和风险
 
-遇到本轮新增的关键设计决策时，按 `.agents/rules/no-mid-flow-questions.md` 判据写入 `## 未决问题`，并回写 `HD-` 账本行。
+遇到本轮新增的关键设计决策时，按 `.agents/rules/no-mid-flow-questions.md` 判据，把详情块（背景/选项/影响/推荐）写入方案产物的 `## 人工裁决待办` 段 `### HD-N：<标题> [needs-human-decision]`（`HD-N` 全局唯一，规则见 `.agents/rules/review-handshake.md`），并回写 `HD-` 账本行（evidence 指向 `{plan-artifact}#HD-N`）；普通未决问题仍写 `## 未决问题`。
 
 **设计原则**：
 1. **架构合理性**：选择结构正确的方案，改动大小不是首要依据。不要为了减少 diff 而在不合理的结构上叠加
@@ -122,7 +124,6 @@ date "+%Y-%m-%d %H:%M:%S%:z"
 - `assigned_to`：{当前 AI 代理}
 - `updated_at`：{当前时间}
 - `agent_infra_version`：按 `.agents/rules/version-stamp.md` 取值
-- 若 `target_date` 为空，基于工作量评估写入预估完成日（`YYYY-MM-DD`）；无法合理预估时保持留空、不阻塞；已有值则保留
 - 记录本轮方案产物：`{plan-artifact}`（Round `{plan-round}`）
 - 如任务模板包含 `## 设计` 段落，更新为指向 `{plan-artifact}` 的链接
 - 在工作流进度中标记 technical-design 为已完成，并注明实际轮次（如果任务模板支持）

package/templates/.agents/skills/post-release/SKILL.en.md

@@ -1,6 +1,8 @@
 ---
 name: post-release
-description: "Run post-release follow-up tasks"
+description: >
+  Run post-release follow-up tasks.
+  Use when a release has shipped and follow-up housekeeping is needed.
 ---
 
 # Post-release Tasks

package/templates/.agents/skills/post-release/SKILL.zh-CN.md

@@ -1,6 +1,8 @@
 ---
 name: post-release
-description: "执行版本发布后的后处理工作"
+description: >
+  执行版本发布后的后处理工作。
+  当版本已发布、需要执行发版后的收尾工作时使用。
 ---
 
 # 发布后处理

package/templates/.agents/skills/refine-title/SKILL.en.md

@@ -1,6 +1,8 @@
 ---
 name: refine-title
-description: "Rewrite an Issue or PR title in Conventional Commits format"
+description: >
+  Rewrite an Issue or PR title in Conventional Commits format.
+  Use when an Issue or PR title needs rewriting into Conventional Commits format.
 ---
 
 # Refine Title

package/templates/.agents/skills/refine-title/SKILL.zh-CN.md

@@ -1,6 +1,8 @@
 ---
 name: refine-title
-description: "重构 Issue/PR 标题为 Conventional Commits 格式"
+description: >
+  重构 Issue/PR 标题为 Conventional Commits 格式。
+  当某个 Issue/PR 标题需要改写为 Conventional Commits 格式时使用。
 ---
 
 # 重构标题

package/templates/.agents/skills/release/SKILL.en.md

@@ -1,6 +1,8 @@
 ---
 name: release
-description: "Run the version release workflow"
+description: >
+  Run the version release workflow.
+  Use when you are ready to cut and publish a new version.
 ---
 
 # Version Release

package/templates/.agents/skills/release/SKILL.zh-CN.md

@@ -1,6 +1,8 @@
 ---
 name: release
-description: "执行版本发布流程"
+description: >
+  执行版本发布流程。
+  当准备切出并发布新版本时使用。
 ---
 
 # 版本发布

package/templates/.agents/skills/restore-task/SKILL.en.md

@@ -1,6 +1,8 @@
 ---
 name: restore-task
-description: "Restore local task files from platform Issue comments"
+description: >
+  Restore local task files from platform Issue comments.
+  Use when local task files are missing and need rebuilding from platform Issue comments.
 ---
 
 # Restore Task

package/templates/.agents/skills/restore-task/SKILL.zh-CN.md

@@ -1,6 +1,8 @@
 ---
 name: restore-task
-description: "从平台 Issue 评论还原本地任务文件"
+description: >
+  从平台 Issue 评论还原本地任务文件。
+  当本地任务文件缺失、需要从平台 Issue 评论还原时使用。
 ---
 
 # 还原任务

package/templates/.agents/skills/review-analysis/SKILL.en.md

@@ -1,6 +1,8 @@
 ---
 name: review-analysis
-description: "Review the requirement analysis artifact"
+description: >
+  Review the requirement analysis artifact.
+  Use when a requirements analysis needs an independent review before planning.
 ---
 
 # Requirement Analysis Review
@@ -52,7 +54,7 @@ Record `{analysis-artifact}`, `{review-round}`, and `{review-artifact}` (`review
 
 ### 3. Read Analysis Context
 
-Read `{analysis-artifact}`, `task.md`, and Issue context when available.
+Read `{analysis-artifact}`, `task.md`, and Issue context when available. After reading, record the actually reviewed highest-round analysis artifact by filename in the report's `Review Input` field; leave it blank when it cannot be reliably determined—do not fabricate.
 
 ### 4. Perform Review
 
@@ -77,6 +79,8 @@ date "+%Y-%m-%d %H:%M:%S%:z"
 Set `current_step` to `requirement-analysis-review`, refresh task metadata, and append:
 `- {YYYY-MM-DD HH:mm:ss±HH:MM} — **Review Analysis (Round {N})** by {agent} — Verdict: {Approved/Changes Requested/Rejected}, blockers: {n}, major: {n}, minor: {n}[ (+ {n} env-blocked)] → {review-artifact}`
 
+`env-blocked` is the data source for the `Manual-verify` count folded into review rows in `ai task log`; do not add a parallel manual-verification field.
+
 If task.md has a valid `issue_number`, read `.agents/rules/issue-sync.md`, sync the task comment, and publish the `{review-artifact}` comment.
 
 ### 7. Run Completion Gate

package/templates/.agents/skills/review-analysis/SKILL.zh-CN.md

@@ -1,6 +1,8 @@
 ---
 name: review-analysis
-description: "审查需求分析报告"
+description: >
+  审查需求分析报告。
+  当需求分析需要在进入方案前接受独立审查时使用。
 ---
 
 # 需求分析审查
@@ -58,7 +60,7 @@ tail .agents/workspace/active/{task-id}/task.md
 
 ### 3. 阅读分析上下文
 
-读取最新 `{analysis-artifact}`、`task.md` 和关联 Issue 上下文（如有）。
+读取最新 `{analysis-artifact}`、`task.md` 和关联 Issue 上下文（如有）。读取后，把本轮实际检视的最高轮 analysis artifact 文件名回填到报告 `审查输入` 段；无法可靠取得时留空，不要伪造。
 
 ### 4. 执行审查
 
@@ -88,6 +90,8 @@ date "+%Y-%m-%d %H:%M:%S%:z"
 - 追加：
   `- {YYYY-MM-DD HH:mm:ss±HH:MM} — **Review Analysis (Round {N})** by {agent} — Verdict: {Approved/Changes Requested/Rejected}, blockers: {n}, major: {n}, minor: {n}[ (+ {n} env-blocked)] → {review-artifact}`
 
+`env-blocked` 是 `ai task log` 中 review 行「人工校验点」（EN `Manual-verify`）计数的数据源；不要新增并行人工验证字段。
+
 如果 task.md 中存在有效的 `issue_number`，执行前先读取 `.agents/rules/issue-sync.md`，完成 upstream 仓库检测和权限检测，然后同步 task 评论并发布 `{review-artifact}` 评论。
 
 ### 7. 完成校验

package/templates/.agents/skills/review-analysis/reference/output-templates.en.md

@@ -16,7 +16,7 @@ Rules:
 - If `Blocker > 0`, never use an approved template
 - Never count env-blocked items as blocker / major / minor or use them to trigger Scenario B/C/D
 - The selected scenario must include all TUI command formats
-- The count line always shows 4 numbers: the first three (Blockers / Major / Minor) must be 0 to proceed; the fourth, `Human-decision` (`{h}`), is the number of rows in task.md `## 审查分歧账本` with `stage=analysis` and `status=needs-human-decision` — a "pending human ruling" item that need not be zero and does not participate in scenario selection
+- The count line always shows 4 numbers: the first three (Blockers / Major / Minor) must be 0 to proceed; the fourth, `Human-decision` (`{h}`), is the number of rows in task.md `## 审查分歧账本` with `stage=analysis` and `status=needs-human-decision` — a "pending human ruling" item that need not be zero and does not participate in scenario selection. When `{h} > 0`, before the selected scenario's "Next steps" commands you must expand each pending ruling per the "Pending human-decision pre-block" in `.agents/rules/next-step-output.md` and prompt to resolve them first
 
 ### Scenario A: Approved with no findings
 

package/templates/.agents/skills/review-analysis/reference/output-templates.zh-CN.md

@@ -16,7 +16,7 @@
 - 只要 `Blocker > 0`，就绝对不能输出通过模板
 - env-blocked 项绝对不能被计入 blocker / major / minor 计数，也不能用作触发场景 B/C/D 的依据
 - 所选场景中必须包含所有 TUI 命令格式
-- 计数行固定显示 4 个数字：前三项（阻塞 / 主要 / 次要）必须为 0 才进下一步；第四项 `人工裁决`（`{h}`）= task.md `## 审查分歧账本` 中 `stage=analysis` 且 `status=needs-human-decision` 的行数，是「待人裁」项、不要求归零，也不参与场景判断
+- 计数行固定显示 4 个数字：前三项（阻塞 / 主要 / 次要）必须为 0 才进下一步；第四项 `人工裁决`（`{h}`）= task.md `## 审查分歧账本` 中 `stage=analysis` 且 `status=needs-human-decision` 的行数，是「待人裁」项、不要求归零，也不参与场景判断。当 `{h} > 0` 时，必须在选定场景的「下一步」命令之前，按 `.agents/rules/next-step-output.md`「人工裁决待办前置块」逐项展开裁决项并提示先完成裁决
 
 ### 场景 A：通过且无问题
 

package/templates/.agents/skills/review-analysis/reference/report-template.en.md

@@ -10,7 +10,7 @@ Use this template when writing `review-analysis.md` or `review-analysis-r{N}.md`
 - **Review Round**: Round {review-round}
 - **Artifact File**: `{review-artifact}`
 - **Review Input**:
-  - `{analysis-artifact}`
+  - `{analysis-artifact}` (the highest-round requirement-analysis artifact actually reviewed, e.g. `analysis-r2.md`; leave blank if it cannot be reliably determined)
 
 ## State Check
 

package/templates/.agents/skills/review-analysis/reference/report-template.zh-CN.md

@@ -10,8 +10,7 @@
 - **审查轮次**：第 {review-round} 轮
 - **产物文件**：`{review-artifact}`
 - **审查输入**：
-  - `{code-artifact}`
-  - `{code-artifact}`（如存在）
+  - `{analysis-artifact}`（本轮实际检视的最高轮需求分析产物，如 `analysis-r2.md`；无法可靠取得则留空）
 
 ## 状态核对
 

package/templates/.agents/skills/review-code/SKILL.en.md

@@ -1,6 +1,8 @@
 ---
 name: review-code
-description: "Review code implementation and output a code review report"
+description: >
+  Review code implementation and output a code review report.
+  Use when a code implementation needs review before merging.
 ---
 
 # Code Review
@@ -67,7 +69,7 @@ Scan the task directory and record:
 
 ### 3. Read Implementation and Refinement Context
 
-Read the highest-round code artifact and, if present, the highest-round fix artifact.
+Read the highest-round code artifact and, if present, the highest-round fix artifact. After reading, record the actually reviewed highest-round code artifact (and the highest-round fix artifact, if present) by filename in the report's `Review Input` field; leave it blank when it cannot be reliably determined—do not fabricate.
 
 ### 4. Perform the Review
 
@@ -97,6 +99,7 @@ Update task.md and append:
 `- {YYYY-MM-DD HH:mm:ss±HH:MM} — **Review Code (Round {N})** by {agent} — Verdict: {Approved/Changes Requested/Rejected}, blockers: {n}, major: {n}, minor: {n}[ (+ {n} env-blocked)] → {artifact-filename}`
 
 Omit the bracketed segment when env-blocked = 0; append ` (+ {n} env-blocked)` when env-blocked > 0.
+`env-blocked` is the data source for the `Manual-verify` count folded into review rows in `ai task log`; do not add a parallel manual-verification field.
 
 If task.md contains a valid `issue_number`, perform these sync actions (skip and continue on any failure):
 - Read `.agents/rules/issue-sync.md` before syncing, and complete upstream repository detection plus permission detection