@fitlab-ai/agent-infra 0.4.1 → 0.4.2

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

@@ -9,38 +9,47 @@ description: "创建 Pull Request 到目标分支"
 
 ## 执行流程
 
-### 1. 确定目标分支
+### 1. 解析命令参数
+
+从命令参数中识别：
+- 匹配 `TASK-{yyyyMMdd-HHmmss}` 格式的参数 -> `{task-id}`
+- 其余参数 -> `{target-branch}`
+
+如果提供了 `{task-id}`，读取 `.agents/workspace/active/{task-id}/task.md` 获取任务信息（例如 `issue_number`、`type` 等）。
+如果未提供，可从当前 session 上下文获取；仍无法确定 `{task-id}` 时，后续步骤中的任务关联逻辑跳过。
+
+### 2. 确定目标分支
 
 如果用户显式提供参数就直接使用；否则根据 Git 历史和分支拓扑自动推断。
 
 > 详细分支判断规则见 `reference/branch-strategy.md`。自动推断 base 分支前，先读取 `reference/branch-strategy.md`。
 
-### 2. 准备 PR 正文
+### 3. 准备 PR 正文
 
 读取 `.github/PULL_REQUEST_TEMPLATE.md`（如存在），参考最近合并的 PR 风格，并收集 `<target-branch>` 到 `HEAD` 的全部提交。
 
 > 模板处理、HEREDOC 正文生成和 `Generated with AI assistance` 要求见 `reference/pr-body-template.md`。编写正文前先读取 `reference/pr-body-template.md`。
 
-### 3. 检查远程分支状态
+### 4. 检查远程分支状态
 
 确认当前分支是否已有 upstream；必要时执行 `git push -u origin <current-branch>`。
 
-### 4. 创建 PR
+### 5. 创建 PR
 
 使用 `gh pr create --base <target-branch> --title "<title>" --assignee @me --body ...` 创建 PR。
 
-如果关联任务提供了 `issue_number`，必须在 PR 正文中保留 `Closes #{issue-number}`。
+如果获取到 `{task-id}` 且对应任务提供了 `issue_number`，必须在 PR 正文中保留 `Closes #{issue-number}`。
 
-### 5. 同步 PR 元数据
+### 6. 同步 PR 元数据
 
-对任务关联 PR，立即同步这些核心元数据：
+对获取到 `{task-id}` 的 PR，立即同步这些核心元数据：
 - 执行 `gh label list --search "type:" --limit 1 --json name --jq 'length'`
 - 使用 `gh pr edit {pr-number} --add-label "{type-label}"` 添加 type label
 - 使用 `gh pr edit {pr-number} --add-label "in: {module}"` 添加相关 `in:` labels
 - 使用 `gh pr edit {pr-number} --milestone "{milestone-title}"` 设置里程碑
 - 通过 `Closes #{issue-number}` 保持 Development 关联
 
-### 6. 更新任务状态
+### 7. 更新任务状态
 
 获取当前时间：
 
@@ -48,9 +57,9 @@ description: "创建 Pull Request 到目标分支"
 date "+%Y-%m-%d %H:%M:%S"
 ```
 
-如果当前 PR 关联任务，更新 task.md 的 `pr_number`、`updated_at`，并追加 PR Created 的 Activity Log。
+如果获取到了 `{task-id}`，更新 task.md 的 `pr_number`、`updated_at`，并追加 PR Created 的 Activity Log。
 
-### 7. 告知用户
+### 8. 告知用户
 
 说明 PR URL、元数据同步结果，并按顺序给出两个后续动作：
 - 可选执行 `sync-pr {task-id}`，发布面向 reviewer 的上下文摘要
@@ -59,7 +68,7 @@ date "+%Y-%m-%d %H:%M:%S"
 ## 注意事项
 
 - 必须检查分支中的全部提交，而不是只看最后一个
-- `create-pr` 不能把 type label 映射委托给 `sync-pr`，必须在本技能内内联处理
+- `create-pr` 不能把 type label 映射委托给 `sync-pr`，必须在获取到 `{task-id}` 时于本技能内内联处理
 - 如果从 Issue 继承元数据失败，继续使用 task.md 和分支推断兜底
 
 ## 错误处理

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

@@ -24,7 +24,7 @@ After executing this skill, you **must** immediately update task status in task.
 ### 1. Parse the User Description
 
 Extract from the natural-language description:
-- **Task title**: a concise title (maximum 50 characters)
+- **Task title**: a concise title (maximum 50 characters), in the same language as the user's description
 - **Task type**: `feature` | `bugfix` | `refactor` | `docs` | `chore` (infer from the description)
 - **Workflow**: `feature-development` | `bug-fix` | `refactoring` (infer from the type)
 - **Detailed description**: the cleaned-up original user request

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

@@ -24,7 +24,7 @@ description: "根据自然语言描述创建任务"
 ### 1. 解析用户描述
 
 从自然语言描述中提取：
-- **任务标题**：简洁标题（最多 50 个字符）
+- **任务标题**：简洁标题（最多 50 个字符），使用与用户描述相同的语言
 - **任务类型**：`feature` | `bugfix` | `refactor` | `docs` | `chore`（从描述推断）
 - **工作流**：`feature-development` | `bug-fix` | `refactoring`（从类型推断）
 - **详细描述**：整理后的用户原始描述

package/templates/.agents/skills/implement-task/SKILL.md

@@ -71,6 +71,7 @@ Update `.agents/workspace/active/{task-id}/task.md`:
 - `current_step`: implementation
 - `assigned_to`: {current agent}
 - `updated_at`: {current time}
+- review the `## Requirements` section and only change items from `- [ ]` to `- [x]` when they are clearly satisfied by this round's implemented code and passing tests
 - record `{implementation-artifact}` for Round `{implementation-round}`
 - append:
   `- {yyyy-MM-dd HH:mm:ss} — **Implementation (Round {N})** by {agent} — Code implemented, {n} files modified, {n} tests passed → {implementation-artifact}`

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

@@ -71,6 +71,7 @@ date "+%Y-%m-%d %H:%M:%S"
 - `current_step`：implementation
 - `assigned_to`：{当前代理}
 - `updated_at`：{当前时间}
+- 审查 `## 需求` 段落，仅把本轮已由代码实现且有测试通过支撑的条目从 `- [ ]` 勾为 `- [x]`
 - 记录 Round `{implementation-round}` 的 `{implementation-artifact}`
 - 追加：
   `- {yyyy-MM-dd HH:mm:ss} — **Implementation (Round {N})** by {agent} — Code implemented, {n} files modified, {n} tests passed → {implementation-artifact}`

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

@@ -22,6 +22,7 @@ gh issue view <issue-number> --json number,title,body,labels
 ```
 
 Extract: issue number, title, description, and labels.
+Use the Issue title as-is for the task title (preserve the Issue's original language).
 
 ### 2. Check for an Existing Task
 

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

@@ -22,6 +22,7 @@ gh issue view <issue-number> --json number,title,body,labels
 ```
 
 提取：issue 编号、标题、描述、标签。
+任务标题直接使用 Issue 的原始标题（保持 Issue 标题的原始语言）。
 
 ### 2. 检查已有任务
 

package/templates/.agents/skills/refine-task/SKILL.md

@@ -54,8 +54,10 @@ Get the current time:
 date "+%Y-%m-%d %H:%M:%S"
 ```
 
-Update task.md and append:
-`- {yyyy-MM-dd HH:mm:ss} — **Refinement (Round {N}, for {review-artifact})** by {agent} — Fixed {n} blockers, {n} major, {n} minor issues → {refinement-artifact}`
+Update task.md:
+- review the `## Requirements` section and only change items from `- [ ]` to `- [x]` when they are newly satisfied by this round's fixes and passing tests
+- append:
+  `- {yyyy-MM-dd HH:mm:ss} — **Refinement (Round {N}, for {review-artifact})** by {agent} — Fixed {n} blockers, {n} major, {n} minor issues → {refinement-artifact}`
 
 ### 7. Inform User
 

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

@@ -54,8 +54,10 @@ description: "处理代码审查反馈并修复问题"
 date "+%Y-%m-%d %H:%M:%S"
 ```
 
-更新 task.md，并追加：
-`- {yyyy-MM-dd HH:mm:ss} — **Refinement (Round {N}, for {review-artifact})** by {agent} — Fixed {n} blockers, {n} major, {n} minor issues → {refinement-artifact}`
+更新 task.md：
+- 审查 `## 需求` 段落，仅把因本轮修复而新满足且有测试通过支撑的条目从 `- [ ]` 勾为 `- [x]`
+- 追加：
+  `- {yyyy-MM-dd HH:mm:ss} — **Refinement (Round {N}, for {review-artifact})** by {agent} — Fixed {n} blockers, {n} major, {n} minor issues → {refinement-artifact}`
 
 ### 7. 告知用户
 

package/templates/.agents/skills/sync-issue/SKILL.md

@@ -5,7 +5,7 @@ description: "Sync task progress to a GitHub Issue"
 
 # Sync Progress to Issue
 
-Sync the task state, delivery summary, and published artifacts to the related GitHub Issue.
+Sync the task state, summary comment, and published artifacts to the related GitHub Issue.
 
 ## Execution Flow
 
@@ -35,32 +35,35 @@ Extract `issue_number`, `type`, task title, status, `current_step`, and timestam
 
 Read the highest-round `analysis.md` / `analysis-r{N}.md`, `plan.md` / `plan-r{N}.md`, and the current implementation, refinement, and review artifacts that still exist.
 
-### 5. Detect Delivery Status
-
-> Delivery-mode detection, protected-branch checks, PR-state rules, absolute commit/PR links, and the completed/PR/in-development mode matrix live in `reference/delivery-detection.md`. Read `reference/delivery-detection.md` before summarizing delivery status.
-
-### 6. Sync Labels and Issue Type
+### 5. Sync Labels and Issue Type
 
 > Label initialization, `status:` replacement rules, `in:` label discovery, and the `issue-types` mapping logic live in `reference/label-sync.md`. Read `reference/label-sync.md` before editing Issue metadata.
 
-### 7. Sync Development Linking
+### 6. Sync Development Linking
 
 If `pr_number` exists, make sure the PR body contains one of:
 - `Closes #{issue-number}`
 - `Fixes #{issue-number}`
 - `Resolves #{issue-number}`
 
-### 8. Sync the Milestone
+### 7. Sync the Milestone
 
 > Milestone inheritance, line-branch inference, and `General Backlog` fallback rules live in `reference/milestone-sync.md`. Read `reference/milestone-sync.md` before editing the Issue milestone.
 
+### 8. Sync Requirement Checkboxes
+
+Extract checked `- [x]` items from the `## Requirements` section of task.md; if none exist, skip this step.
+Read the current Issue body with `gh issue view {issue-number} --json body --jq '.body'`.
+Match by checkbox text and replace only `- [ ] {text}` with `- [x] {text}` in the Issue body; keep existing `- [x]` items, unmatched items, and non-requirement checkboxes unchanged.
+Only when the body actually changes, update the full body with `gh api` PATCH and build the request payload with `cat <<'EOF'` heredoc.
+
 ### 9. Publish Context Artifacts
 
-> Existing-comment discovery, hidden markers, the artifact timeline, summary comment ordering, and absolute artifact-link rules live in `reference/comment-publish.md`. Read `reference/comment-publish.md` before publishing Issue comments.
+> Existing-comment discovery, hidden markers, the artifact timeline, and summary comment ordering live in `reference/comment-publish.md`. Read `reference/comment-publish.md` before publishing Issue comments.
 
 > **Shell Safety Rules** (read before publishing comments):
 > 1. `{comment-body}` must be replaced with **actual inline text**. Read the file with the Read tool first, then paste the full content into the heredoc body. **Do NOT** use `$(cat ...)`, `$(< ...)`, `$(...)`, or `${...}` inside `<<'EOF'`. Quoted heredocs suppress all command substitution and variable expansion, so those expressions will be output as literal text.
-> 2. When constructing strings that contain `<!-- -->`, **do NOT use `echo`**. In bash/zsh, `echo` escapes `!` as `\!`, which makes hidden markers visible. Build all comment content with `cat <<'EOF'` heredocs or `printf '%s\n'`.
+> 2. When constructing strings that contain `<!-- -->`, **do NOT use `echo`**. In bash/zsh, `echo` escapes `!` as `\!`, which makes hidden markers visible. Build all comment content and the Step 8 Issue body update with `cat <<'EOF'` heredocs or `printf '%s\n'`.
 
 ### 10. Update Task Status
 
@@ -79,9 +82,8 @@ Summarize synced labels, milestone, development linkage, published comments, and
 ## Notes
 
 - The hidden comment marker format must stay `<!-- sync-issue:{task-id}:{file-stem} -->`
-- Use absolute links such as `https://github.com/{owner}/{repo}/commit/{commit-hash}` and `https://github.com/{owner}/{repo}/pull/{pr-number}`
 - Build the artifact timeline from Activity Log order, not a fixed `analysis -> plan -> implementation -> review -> summary` sequence
-- Follow the Step 9 shell safety rules when publishing comments: do not rely on command substitution inside quoted heredocs, and do not use `echo` for HTML comment markers
+- Follow the Step 9 shell safety rules when publishing comments or updating the Issue body: do not rely on command substitution inside quoted heredocs, and do not use `echo` for HTML comment markers
 
 ## Error Handling
 

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

@@ -5,7 +5,7 @@ description: "将任务进度同步到 GitHub Issue"
 
 # 同步进度到 Issue
 
-把任务状态、交付摘要和产物发布时间线同步到关联的 GitHub Issue。
+把任务状态、摘要评论和产物发布时间线同步到关联的 GitHub Issue。
 
 ## 执行流程
 
@@ -35,32 +35,35 @@ grep -rl "^issue_number: {issue-number}$" \
 
 读取最高轮次的 `analysis.md` / `analysis-r{N}.md`、`plan.md` / `plan-r{N}.md`，以及仍然存在的实现、修复、审查产物。
 
-### 5. 探测交付状态
-
-> 交付模式探测、受保护分支检查、PR 状态判断、绝对 commit/PR 链接，以及完成/PR 阶段/开发中模式矩阵见 `reference/delivery-detection.md`。汇总交付状态前先读取 `reference/delivery-detection.md`。
-
-### 6. 同步 Labels 和 Issue Type
+### 5. 同步 Labels 和 Issue Type
 
 > label 初始化、`status:` 替换规则、`in:` label 发现，以及 `issue-types` 映射逻辑见 `reference/label-sync.md`。编辑 Issue 元数据前先读取 `reference/label-sync.md`。
 
-### 7. 同步 Development 关联
+### 6. 同步 Development 关联
 
 如果存在 `pr_number`，确保 PR 正文包含以下任一项：
 - `Closes #{issue-number}`
 - `Fixes #{issue-number}`
 - `Resolves #{issue-number}`
 
-### 8. 同步里程碑
+### 7. 同步里程碑
 
 > milestone 继承、版本分支推断和 `General Backlog` 回退规则见 `reference/milestone-sync.md`。编辑 Issue milestone 前先读取 `reference/milestone-sync.md`。
 
+### 8. 同步需求复选框
+
+从 task.md 的 `## 需求` 段落提取已勾选的 `- [x]` 项；如果没有，跳过。
+读取 Issue 当前正文：`gh issue view {issue-number} --json body --jq '.body'`。
+按复选框文本匹配，将 Issue body 中对应的 `- [ ] {text}` 单向替换为 `- [x] {text}`；已有 `- [x]`、未匹配项和非需求复选框保持不变。
+只有在正文实际变化时，才使用 `gh api` PATCH 更新完整 body，并用 `cat <<'EOF'` heredoc 构造请求内容。
+
 ### 9. 发布上下文产物
 
-> 已有评论探测、隐藏标记、产物时间线、summary 评论顺序，以及绝对产物链接规则见 `reference/comment-publish.md`。发布 Issue 评论前先读取 `reference/comment-publish.md`。
+> 已有评论探测、隐藏标记、产物时间线和 summary 评论顺序见 `reference/comment-publish.md`。发布 Issue 评论前先读取 `reference/comment-publish.md`。
 
 > **Shell 安全规则**（发布评论前必读）：
 > 1. `{comment-body}` 必须替换为**实际的内联文本**。先用 Read 工具读取文件，再将全文粘贴到 heredoc body 中。**禁止**在 `<<'EOF'` 内部使用 `$(cat ...)`、`$(< ...)`、`$(...)`、`${...}`。带引号 heredoc 会阻止所有命令替换和变量展开，它们会被当作字面文本输出。
-> 2. 构造含 `<!-- -->` 的字符串时，**禁止使用 `echo`**。bash/zsh 中 `echo` 会将 `!` 转义为 `\!`，导致隐藏标识可见。所有评论内容统一使用 `cat <<'EOF'` heredoc 或 `printf '%s\n'` 构造。
+> 2. 构造含 `<!-- -->` 的字符串时，**禁止使用 `echo`**。bash/zsh 中 `echo` 会将 `!` 转义为 `\!`，导致隐藏标识可见。所有评论内容以及步骤 8 的 Issue body 更新都统一使用 `cat <<'EOF'` heredoc 或 `printf '%s\n'` 构造。
 
 ### 10. 更新任务状态
 
@@ -79,9 +82,8 @@ date "+%Y-%m-%d %H:%M:%S"
 ## 注意事项
 
 - 隐藏评论标记必须保持为 `<!-- sync-issue:{task-id}:{file-stem} -->`
-- 必须使用绝对链接，例如 `https://github.com/{owner}/{repo}/commit/{commit-hash}` 和 `https://github.com/{owner}/{repo}/pull/{pr-number}`
 - 产物时间线按 Activity Log 顺序构建，而不是固定的 `analysis -> plan -> implementation -> review -> summary`
-- 发布评论时遵守步骤 9 的 Shell 安全规则，不要在带引号 heredoc 中依赖命令替换，也不要用 `echo` 构造 HTML 注释标记
+- 发布评论和更新 Issue body 时遵守步骤 9 的 Shell 安全规则，不要在带引号 heredoc 中依赖命令替换，也不要用 `echo` 构造 HTML 注释标记
 
 ## 错误处理
 

package/templates/.agents/skills/sync-issue/reference/comment-publish.md

@@ -81,8 +81,4 @@ EOF
 )"
 ```
 
-Required link formats:
-- `https://github.com/{owner}/{repo}/commit/{commit-hash}`
-- `https://github.com/{owner}/{repo}/pull/{pr-number}`
-
 Do not fall back to a fixed `analysis -> plan -> implementation -> review -> summary` order.

package/templates/.agents/skills/sync-issue/reference/comment-publish.zh-CN.md

@@ -81,8 +81,4 @@ EOF
 )"
 ```
 
-必须使用以下绝对链接格式：
-- `https://github.com/{owner}/{repo}/commit/{commit-hash}`
-- `https://github.com/{owner}/{repo}/pull/{pr-number}`
-
 不要回退到固定的 `analysis -> plan -> implementation -> review -> summary` 顺序。

package/templates/.agents/skills/sync-issue/reference/label-sync.md

@@ -24,12 +24,11 @@ Status decision table:
 
 | Condition | Action |
 |---|---|
+| Issue is closed (`state = CLOSED`) | add no new `status:` label |
+| task lives under `completed/` | add no new `status:` label |
 | task lives under `blocked/` | add `status: blocked` |
-| Scenario A: completed | add no new `status:` label |
-| Scenario B: PR is `MERGED` | add no new `status:` label |
-| Scenario B: PR is `OPEN` | add `status: in-progress` |
-| Scenario C + `current_step` ∈ {`requirement-analysis`, `technical-design`} | add `status: pending-design-work` |
-| Scenario C + `current_step` ∈ {`implementation`, `code-review`, `refinement`} | add `status: in-progress` |
+| `current_step` ∈ {`requirement-analysis`, `technical-design`} | add `status: pending-design-work` |
+| `current_step` ∈ {`implementation`, `code-review`, `refinement`} | add `status: in-progress` |
 
 `in:` label workflow:
 

package/templates/.agents/skills/sync-issue/reference/label-sync.zh-CN.md

@@ -24,12 +24,11 @@ gh issue edit {issue-number} --add-label "{status-label}"
 
 | 条件 | 操作 |
 |---|---|
+| Issue 已关闭（`state = CLOSED`） | 不新增 `status:` label |
+| 任务位于 `completed/` 目录下 | 不新增 `status:` label |
 | 任务位于 `blocked/` 目录下 | 添加 `status: blocked` |
-| 场景 A：已完成 | 不新增 `status:` label |
-| 场景 B：PR 状态为 `MERGED` | 不新增 `status:` label |
-| 场景 B：PR 状态为 `OPEN` | 添加 `status: in-progress` |
-| 场景 C + `current_step` ∈ {`requirement-analysis`, `technical-design`} | 添加 `status: pending-design-work` |
-| 场景 C + `current_step` ∈ {`implementation`, `code-review`, `refinement`} | 添加 `status: in-progress` |
+| `current_step` ∈ {`requirement-analysis`, `technical-design`} | 添加 `status: pending-design-work` |
+| `current_step` ∈ {`implementation`, `code-review`, `refinement`} | 添加 `status: in-progress` |
 
 `in:` label 工作流：
 

package/templates/.agents/skills/sync-pr/SKILL.md

@@ -9,33 +9,47 @@ Sync PR metadata and keep one reviewer-facing summary comment up to date.
 
 ## Execution Flow
 
-### 1. Verify the Task Exists
+### 1. Parse the Argument
 
-Check `.agents/workspace/active/{task-id}/task.md` and stop if the task does not exist.
+Accept either `task-id` or PR number. For PR-number input, resolve the task with:
 
-### 2. Read Task Information
+```bash
+grep -rl "^pr_number: {pr-number}$" \
+  .agents/workspace/active/ \
+  .agents/workspace/blocked/ \
+  .agents/workspace/completed/ \
+  2>/dev/null | head -1
+```
+
+If no task matches, output `No task found associated with PR #{pr-number}`.
+
+### 2. Verify the Task Exists
+
+Search active, blocked, and completed task directories and lock onto the matching task folder before continuing.
+
+### 3. Read Task Information
 
 Extract `pr_number`, `issue_number`, task title, type, and the latest timestamps from task.md.
 
-### 3. Read Context Files
+### 4. Read Context Files
 
 Read the latest plan, implementation, review, and refinement artifacts that will inform PR metadata and the reviewer summary.
 
-### 4. Resolve Repository Coordinates and Label Readiness
+### 5. Resolve Repository Coordinates and Label Readiness
 
 Resolve `repo="$(gh repo view --json nameWithOwner --jq '.nameWithOwner')"` and verify whether `type:` labels have been initialized.
 
-### 5. Sync Metadata
+### 6. Sync Metadata
 
 Sync the mapped type label, relevant `in:` labels, and milestone onto the PR.
 
 > PR-state safeguards, milestone inference, and metadata skip rules for closed or merged PRs live in `reference/delivery-detection.md`. Read `reference/delivery-detection.md` before editing PR metadata.
 
-### 6. Sync Development Linking
+### 7. Sync Development Linking
 
 If `issue_number` exists, ensure the PR body contains `Closes #{issue-number}` or an equivalent closing keyword.
 
-### 7. Publish the Reviewer Summary
+### 8. Publish the Reviewer Summary
 
 > Hidden markers, idempotent summary comment updates, review-history formatting, and comment create/update rules live in `reference/comment-publish.md`. Read `reference/comment-publish.md` before publishing the summary.
 
@@ -43,7 +57,7 @@ If `issue_number` exists, ensure the PR body contains `Closes #{issue-number}` o
 > 1. `{comment-body}` must be replaced with **actual inline text**. Read the file with the Read tool first, then paste the full content into the heredoc body. **Do NOT** use `$(cat ...)`, `$(< ...)`, `$(...)`, or `${...}` inside `<<'EOF'`. Quoted heredocs suppress all command substitution and variable expansion, so those expressions will be output as literal text.
 > 2. When constructing strings that contain `<!-- -->`, **do NOT use `echo`**. In bash/zsh, `echo` escapes `!` as `\!`, which makes hidden markers visible. Build all comment content with `cat <<'EOF'` heredocs or `printf '%s\n'`.
 
-### 8. Update Task Status
+### 9. Update Task Status
 
 Get the current time:
 
@@ -53,7 +67,7 @@ date "+%Y-%m-%d %H:%M:%S"
 
 Update `last_synced_to_pr_at` and append the Sync to PR Activity Log entry.
 
-### 9. Inform the User
+### 10. Inform the User
 
 Report the synchronized labels, milestone, development status, summary result, and PR URL.
 
@@ -62,10 +76,11 @@ Report the synchronized labels, milestone, development status, summary result, a
 - The hidden summary marker must stay `<!-- sync-pr:{task-id}:summary -->`
 - Keep exactly one summary comment for reviewers
 - If the PR is already closed or merged, report `PR #{number} is closed/merged, metadata sync skipped`
-- Follow the Step 7 shell safety rules when publishing comments: do not rely on command substitution inside quoted heredocs, and do not use `echo` for HTML comment markers
+- Follow the Step 8 shell safety rules when publishing comments: do not rely on command substitution inside quoted heredocs, and do not use `echo` for HTML comment markers
 
 ## Error Handling
 
+- No task found for the PR: `No task found associated with PR #{pr-number}`
 - Task not found: `Task {task-id} not found`
 - Missing PR number: `Task has no pr_number field`
 - PR not found: `PR #{number} not found`

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

@@ -9,33 +9,47 @@ description: "将任务进度同步到 Pull Request"
 
 ## 执行流程
 
-### 1. 验证任务存在
+### 1. 解析参数
 
-检查 `.agents/workspace/active/{task-id}/task.md`；如果任务不存在则立即停止。
+同时接受 `task-id` 和 PR number。对于 PR number，使用下面的命令反查任务：
 
-### 2. 读取任务信息
+```bash
+grep -rl "^pr_number: {pr-number}$" \
+  .agents/workspace/active/ \
+  .agents/workspace/blocked/ \
+  .agents/workspace/completed/ \
+  2>/dev/null | head -1
+```
+
+如果没有匹配任务，输出 `No task found associated with PR #{pr-number}`。
+
+### 2. 验证任务存在
+
+按 active、blocked、completed 的顺序定位匹配任务目录，再继续后续步骤。
+
+### 3. 读取任务信息
 
 从 task.md 提取 `pr_number`、`issue_number`、任务标题、type 和最新时间戳。
 
-### 3. 读取上下文文件
+### 4. 读取上下文文件
 
 读取最新的方案、实现、审查和修复产物，用于生成 PR 元数据和 reviewer 摘要。
 
-### 4. 解析仓库坐标并检查 label 就绪状态
+### 5. 解析仓库坐标并检查 label 就绪状态
 
 先解析 `repo="$(gh repo view --json nameWithOwner --jq '.nameWithOwner')"`，再确认 `type:` labels 是否已经初始化。
 
-### 5. 同步元数据
+### 6. 同步元数据
 
 把映射后的 type label、相关 `in:` labels 和 milestone 同步到 PR 上。
 
 > PR 状态保护、milestone 推断，以及 PR 已关闭/已合并时的跳过规则见 `reference/delivery-detection.md`。编辑 PR 元数据前先读取 `reference/delivery-detection.md`。
 
-### 6. 同步 Development 关联
+### 7. 同步 Development 关联
 
 如果存在 `issue_number`，确保 PR 正文包含 `Closes #{issue-number}` 或等价的关闭关键字。
 
-### 7. 发布 reviewer 摘要
+### 8. 发布 reviewer 摘要
 
 > 隐藏标记、幂等 summary 评论更新、review history 格式，以及评论创建/更新规则见 `reference/comment-publish.md`。发布摘要前先读取 `reference/comment-publish.md`。
 
@@ -43,7 +57,7 @@ description: "将任务进度同步到 Pull Request"
 > 1. `{comment-body}` 必须替换为**实际的内联文本**。先用 Read 工具读取文件，再将全文粘贴到 heredoc body 中。**禁止**在 `<<'EOF'` 内部使用 `$(cat ...)`、`$(< ...)`、`$(...)`、`${...}`。带引号 heredoc 会阻止所有命令替换和变量展开，它们会被当作字面文本输出。
 > 2. 构造含 `<!-- -->` 的字符串时，**禁止使用 `echo`**。bash/zsh 中 `echo` 会将 `!` 转义为 `\!`，导致隐藏标识可见。所有评论内容统一使用 `cat <<'EOF'` heredoc 或 `printf '%s\n'` 构造。
 
-### 8. 更新任务状态
+### 9. 更新任务状态
 
 获取当前时间：
 
@@ -53,7 +67,7 @@ date "+%Y-%m-%d %H:%M:%S"
 
 更新 `last_synced_to_pr_at`，并追加 Sync to PR 的 Activity Log。
 
-### 9. 告知用户
+### 10. 告知用户
 
 汇总已同步的 labels、milestone、development 状态、summary 结果以及 PR URL。
 
@@ -62,10 +76,11 @@ date "+%Y-%m-%d %H:%M:%S"
 - 隐藏 summary 标记必须保持 `<!-- sync-pr:{task-id}:summary -->`
 - 面向 reviewer 只保留一条摘要评论
 - 如果 PR 已关闭或已合并，必须报告 `PR #{number} is closed/merged, metadata sync skipped`
-- 发布摘要时遵守步骤 7 的 Shell 安全规则，不要在带引号 heredoc 中依赖命令替换，也不要用 `echo` 构造 HTML 注释标记
+- 发布摘要时遵守步骤 8 的 Shell 安全规则，不要在带引号 heredoc 中依赖命令替换，也不要用 `echo` 构造 HTML 注释标记
 
 ## 错误处理
 
+- 未找到关联任务：`No task found associated with PR #{pr-number}`
 - 任务未找到：`Task {task-id} not found`
 - 缺少 PR 编号：`Task has no pr_number field`
 - PR 不存在：`PR #{number} not found`

package/templates/.agents/skills/sync-pr/reference/comment-publish.zh-CN.md

@@ -13,10 +13,10 @@
 已有评论必须通过 Issues comments API 获取，而不是单独的 PR comments API。
 
 推荐摘要章节：
-- `## Review Summary`
-- `### Key Technical Decisions`
-- `### Review History`
-- `### Test Results`
+- `## 审查摘要`
+- `### 关键技术决策`
+- `### 审查历程`
+- `### 测试结果`
 
 摘要内容规则：
 - 面向 reviewer 编写，而不是面向终端用户

package/templates/.agents/skills/update-agent-infra/scripts/sync-templates.js

@@ -22,6 +22,8 @@ import { fileURLToPath } from 'node:url';
 const DEFAULTS = {
   "files": {
     "managed": [
+      ".agents/QUICKSTART.md",
+      ".agents/README.md",
       ".agents/skills/",
       ".agents/templates/",
       ".agents/workflows/",
@@ -37,28 +39,20 @@ const DEFAULTS = {
       "**/test-integration.*",
       "**/test.*",
       "**/upgrade-dependency.*",
-      ".agents/QUICKSTART.md",
-      ".agents/README.md",
       ".agents/skills/release/SKILL.*",
       ".agents/skills/test-integration/SKILL.*",
       ".agents/skills/test/SKILL.*",
       ".agents/skills/upgrade-dependency/SKILL.*",
-      ".claude/CLAUDE.md",
-      ".claude/project-rules.md",
       ".claude/settings.json",
-      ".codex/README.md",
       ".gemini/settings.json",
       ".github/hooks/pre-commit",
-      ".gitignore",
-      ".opencode/COMMAND_STYLE_GUIDE.md",
-      ".opencode/README.md",
-      "AGENTS.md"
+      ".gitignore"
     ],
     "ejected": []
   }
 };
 
-const INSTALLER_VERSION = "v0.4.1";
+const INSTALLER_VERSION = "v0.4.2";
 
 function norm(p) { return p.replace(/\\/g, '/'); }
 

package/templates/.claude/commands/create-pr.md

@@ -1,6 +1,6 @@
 ---
 description: "Create a Pull Request to a target branch"
-usage: "/create-pr [target-branch]"
+usage: "/create-pr [task-id] [target-branch]"
 ---
 
 Read and execute the create-pr skill from `.agents/skills/create-pr/SKILL.md`.

package/templates/.claude/commands/create-pr.zh-CN.md

@@ -1,6 +1,6 @@
 ---
 description: "创建 Pull Request 到目标分支"
-usage: "/create-pr [target-branch]"
+usage: "/create-pr [task-id] [target-branch]"
 ---
 
 读取并执行 `.agents/skills/create-pr/SKILL.md` 中的 create-pr 技能。

package/templates/.claude/commands/sync-pr.md

@@ -1,6 +1,6 @@
 ---
 description: "Sync task progress to a Pull Request"
-usage: "/sync-pr <task-id>"
+usage: "/sync-pr <task-id | pr-number>"
 ---
 
 Read and execute the sync-pr skill from `.agents/skills/sync-pr/SKILL.md`.

package/templates/.claude/commands/sync-pr.zh-CN.md

@@ -1,6 +1,6 @@
 ---
 description: "将任务进度同步到 Pull Request"
-usage: "/sync-pr <task-id>"
+usage: "/sync-pr <task-id | pr-number>"
 ---
 
 读取并执行 `.agents/skills/sync-pr/SKILL.md` 中的 sync-pr 技能。

package/templates/.gemini/commands/_project_/sync-pr.toml

@@ -1,6 +1,6 @@
 description = "Sync task progress to a Pull Request"
 prompt = """
-Sync task {{args}} to PR.
+Sync PR context: {{args}}
 
 Read and execute the sync-pr skill from `.agents/skills/sync-pr/SKILL.md`.
 

package/templates/.gemini/commands/_project_/sync-pr.zh-CN.toml

@@ -1,6 +1,6 @@
 description = "将任务进度同步到 Pull Request"
 prompt = """
-同步任务 {{args}} 到 PR。
+同步 PR 上下文：{{args}}
 
 读取并执行 `.agents/skills/sync-pr/SKILL.md` 中的 sync-pr 技能。