@fitlab-ai/agent-infra 0.5.7 → 0.5.9

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

@@ -1,11 +1,11 @@
 ---
 name: init-milestones
-description: "初始化仓库的 GitHub Milestones 体系"
+description: "初始化仓库的 milestones 体系"
 ---
 
-# 初始化 GitHub Milestones
+# 初始化 milestones
 
-一次性初始化仓库的标准 GitHub Milestones 体系。
+一次性初始化仓库的标准 milestones 体系。
 
 ## 执行流程
 
@@ -75,10 +75,10 @@ bash .agents/skills/init-milestones/scripts/init-milestones.sh "$ARGUMENTS"
 
 ## 错误处理
 
-- 未找到 `gh`：提示 "GitHub CLI (`gh`) is not installed"
-- 认证失败：提示 "GitHub CLI is not authenticated"
-- 仓库访问失败：提示 "Unable to access the current repository with gh"
+- 未找到平台 CLI：提示 "the platform CLI is not installed"
+- 认证失败：提示 "the platform CLI is not authenticated"
+- 仓库访问失败：提示 "Unable to access the current repository with the platform CLI"
 - 版本解析失败：提示 "Unable to determine current version baseline"
 - `--history` 模式下未找到任何 `v*` git tags：提示 "No history tags found matching v*; only standard milestones will be created"
 - 权限不足：提示 "No permission to manage milestones in this repository"
-- API 限流：提示 "GitHub API rate limit reached, please retry later"
+- API 限流：提示 "platform API rate limit reached, please retry later"

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

@@ -99,7 +99,7 @@ Update `.agents/workspace/active/{task-id}/task.md`:
 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
 - Set `status: pending-design-work` by following issue-sync.md
-- Create or update the `<!-- sync-issue:{task-id}:task -->` comment (follow the task.md comment sync rule in issue-sync.md)
+- Create or update the task comment marker defined in `.agents/rules/issue-sync.md` (follow the task.md comment sync rule in issue-sync.md)
 - Publish the `{plan-artifact}` comment
 
 ### 8. Verification Gate

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

@@ -99,7 +99,7 @@ date "+%Y-%m-%d %H:%M:%S%:z"
 如果 task.md 中存在有效的 `issue_number`，执行以下同步操作（任一失败则跳过并继续）：
 - 执行前先读取 `.agents/rules/issue-sync.md`，完成 upstream 仓库检测和权限检测
 - 按 issue-sync.md 设置 `status: pending-design-work`
-- 创建或更新 `<!-- sync-issue:{task-id}:task -->` 评论（按 issue-sync.md 的 task.md 评论同步规则）
+- 创建或更新 `.agents/rules/issue-sync.md` 中定义的 task 评论标记（按 issue-sync.md 的 task.md 评论同步规则）
 - 发布 `{plan-artifact}` 评论
 
 ### 8. 完成校验

package/templates/.agents/skills/plan-task/config/verify.json

@@ -38,7 +38,9 @@
       "verify_comment_content": true,
       "verify_task_comment_content": true,
       "verify_issue_type": true,
-      "verify_milestone": true
+      "verify_milestone": true,
+      "expected_status_label_key": "pendingDesignWork",
+      "expected_comment_marker_key": "artifact"
     }
   }
 }

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

@@ -62,7 +62,7 @@ Update task.md:
 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
 - Set `status: in-progress` by following issue-sync.md
-- Create or update the `<!-- sync-issue:{task-id}:task -->` comment (follow the task.md comment sync rule in issue-sync.md)
+- Create or update the task comment marker defined in `.agents/rules/issue-sync.md` (follow the task.md comment sync rule in issue-sync.md)
 - Publish the `{refinement-artifact}` comment
 
 ### 7. Verification Gate

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

@@ -62,7 +62,7 @@ date "+%Y-%m-%d %H:%M:%S%:z"
 如果 task.md 中存在有效的 `issue_number`，执行以下同步操作（任一失败则跳过并继续）：
 - 执行前先读取 `.agents/rules/issue-sync.md`，完成 upstream 仓库检测和权限检测
 - 按 issue-sync.md 设置 `status: in-progress`
-- 创建或更新 `<!-- sync-issue:{task-id}:task -->` 评论（按 issue-sync.md 的 task.md 评论同步规则）
+- 创建或更新 `.agents/rules/issue-sync.md` 中定义的 task 评论标记（按 issue-sync.md 的 task.md 评论同步规则）
 - 发布 `{refinement-artifact}` 评论
 
 ### 7. 完成校验

package/templates/.agents/skills/refine-task/config/verify.json

@@ -32,7 +32,9 @@
       "verify_comment_content": true,
       "verify_task_comment_content": true,
       "verify_issue_type": true,
-      "verify_milestone": true
+      "verify_milestone": true,
+      "expected_status_label_key": "inProgress",
+      "expected_comment_marker_key": "artifact"
     }
   }
 }

package/templates/.agents/skills/refine-task/reference/fix-workflow.en.md

@@ -26,11 +26,11 @@ For each fix:
 1. read the affected files
 2. apply the smallest necessary change
 3. verify the change addresses the review feedback
-4. run the relevant tests
+4. run the project's **smoke subset** for immediate feedback (see the `test` skill)
 
 ## Run Test Verification
 
-Run the project test command from the `test` skill and confirm that all required tests still pass.
+Before writing the refinement report, run the project's **core subset** as final verification and confirm that all required tests still pass. If the project does not have layered scripts, fall back to the full project test command.
 
 ## Choose the Next-Step Branch
 

package/templates/.agents/skills/refine-task/reference/fix-workflow.zh-CN.md

@@ -26,11 +26,11 @@
 1. 读取受影响文件
 2. 施加最小必要改动
 3. 验证改动确实解决了审查反馈
-4. 运行相关测试
+4. 运行项目测试的 **smoke 子集**做即时反馈（参见 `test` skill）
 
 ## 运行测试验证
 
-运行项目测试命令。项目测试命令以 `test` skill 为准，并确认所有必需测试仍然通过。
+写 refinement 报告前，运行项目测试的 **core 子集**做最终验证，确保所有必需测试仍然通过。如果项目没有分层 script，回退到完整项目测试命令。
 
 ## 选择下一步分支
 

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

@@ -9,7 +9,7 @@ Restore local task workspace files from platform Issue comments that contain syn
 
 ## Boundary / Critical Rules
 
-- Restore files only from comments marked with `<!-- sync-issue:{task-id}:... -->`
+- Restore files only from comments that match the marker registry in `.agents/rules/issue-sync.md`
 - Restore into `.agents/workspace/active/{task-id}/` by default
 - Stop immediately if the target directory already exists and ask the user to resolve the conflict first
 - After executing this skill, you **must** immediately update the restored `task.md`
@@ -31,16 +31,11 @@ Read all Issue comments by following the "Read Issue comments" command in `.agen
 
 ### 3. Determine the task-id and Files to Restore
 
-Filter comments by these hidden markers:
-
-```html
-<!-- sync-issue:{task-id}:{file-stem} -->
-<!-- sync-issue:{task-id}:{file-stem}:{part}/{total} -->
-```
+Filter comments by the task, artifact, and chunked artifact markers defined in `.agents/rules/issue-sync.md`.
 
 Rules:
 - when `{task-id}` was provided, match only that task
-- when `{task-id}` was omitted, infer it from the `<!-- sync-issue:{task-id}:task -->` comment first
+- when `{task-id}` was omitted, infer it from the task comment marker first
 - if you cannot determine a unique task-id, stop and tell the user
 - ignore `summary` marker comments because they are complete-task aggregate output rather than restorable local task files
 - map `{file-stem}` back to filenames:
@@ -58,7 +53,7 @@ Read `.agents/rules/issue-sync.md` before executing this step.
 For each file:
 - collect its single comment or chunked comments
 - for `task.md` comments, reverse the `<details>` frontmatter wrapper described in issue-sync.md before reassembling the file body
-- when `{part}/{total}` exists, sort by part and verify the set is complete
+- when a chunk marker includes part and total indexes, sort by part and verify the set is complete
 - extract the file body by removing the hidden marker, heading, and footer
 - concatenate chunk bodies into the final file content
 
@@ -88,66 +83,20 @@ Update the restored `task.md`:
 - `status`: `active`
 - `assigned_to`: {current AI agent}
 - `updated_at`: {current time}
-- keep the original `current_step`
-- append this entry to `## Activity Log`:
-  ```
-  - {YYYY-MM-DD HH:mm:ss±HH:MM} — **Restore Task** by {agent} — Restored task from Issue #{issue-number}
-  ```
-
-### 7. Verification Gate
-
-Run the verification gate:
-
-```bash
-node .agents/scripts/validate-artifact.js gate restore-task .agents/workspace/active/{task-id} --format text
-```
-
-Handle the result as follows:
-- exit code 0 (all checks passed) -> continue to the "Inform User" step
-- exit code 1 (validation failed) -> fix the reported issues and run the gate again
-- exit code 2 (network blocked) -> stop and tell the user that human intervention is required
 
-Keep the gate output in your reply as fresh evidence. Do not claim completion without output from this run.
+Append an Activity Log entry indicating the task was restored from the platform Issue.
 
-### 8. Inform User
+### 7. Inform User
 
-> Execute this step only after the verification gate passes.
-
-> **IMPORTANT**: All TUI command formats listed below must be output in full. Do not show only the format for the current AI agent. If `.agents/.airc.json` configures custom TUIs (via `customTUIs`), read each tool's `name` and `invoke`, then add the matching command line in the same format (`${skillName}` becomes the skill name and `${projectName}` becomes the project name).
-
-Output format:
-
-```text
-Task {task-id} was restored from Issue #{issue-number}.
-
-Summary:
-- Restored files: {count}
-- Task directory: .agents/workspace/active/{task-id}/
-- Current step: {current_step}
-
-Next step - check task status:
-  - Claude Code / OpenCode: /check-task {task-id}
-  - Gemini CLI: /{{project}}:check-task {task-id}
-  - Codex CLI: $check-task {task-id}
-```
+Report the restored task id, restored file count, and the active task directory.
 
 ## Completion Checklist
 
-- [ ] Fetched and parsed Issue comments
-- [ ] Restored `task.md` and every available artifact file
-- [ ] Updated the restored task.md
-- [ ] Ran and passed the verification gate
-- [ ] Showed the next-step commands in every TUI format, including any custom TUIs
-
-## STOP
-
-Stop after completing the checklist. Do not continue the workflow automatically.
+- [ ] Fetched Issue comments from the platform
+- [ ] Restored task files locally
+- [ ] Updated restored task metadata
+- [ ] Reported the restored directory
 
-## Error Handling
+### 8. Stop
 
-- Issue missing or inaccessible
-- Platform CLI unavailable or unauthenticated
-- No sync-marked comments found
-- Unable to determine a unique `task-id`
-- Target directory already exists
-- Missing chunks or incomplete chunk ordering
+Stop after the completion checklist. Do not commit automatically.

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

@@ -9,7 +9,7 @@ description: "从平台 Issue 评论还原本地任务文件"
 
 ## 行为边界 / 关键规则
 
-- 只从带 `<!-- sync-issue:{task-id}:... -->` 标记的评论恢复文件
+- 只从匹配 `.agents/rules/issue-sync.md` 标记注册表的评论恢复文件
 - 默认恢复到 `.agents/workspace/active/{task-id}/`
 - 如果目标目录已存在，立即停止并提示用户先处理目录冲突
 - 执行本技能后，你**必须**立即更新恢复出的 `task.md`
@@ -31,16 +31,11 @@ description: "从平台 Issue 评论还原本地任务文件"
 
 ### 3. 确定 task-id 与待恢复文件
 
-从评论中筛选隐藏标记：
-
-```html
-<!-- sync-issue:{task-id}:{file-stem} -->
-<!-- sync-issue:{task-id}:{file-stem}:{part}/{total} -->
-```
+按 `.agents/rules/issue-sync.md` 中定义的 task、artifact 和分片 artifact 标记筛选评论。
 
 处理规则：
 - 用户提供了 `{task-id}` 时，仅匹配该任务
-- 未提供时，优先从 `<!-- sync-issue:{task-id}:task -->` 评论推断
+- 未提供时，优先从 task 评论标记推断
 - 若找不到唯一 task-id，立即停止并告知用户
 - 忽略 `summary` 标记评论；它是 complete-task 的聚合产物，不对应本地任务文件
 - 将 `{file-stem}` 映射回文件名：
@@ -58,7 +53,7 @@ description: "从平台 Issue 评论还原本地任务文件"
 对每个文件执行：
 - 收集单条评论或分片评论
 - 对 `task.md` 评论按 issue-sync.md 中的 `<details>` frontmatter 格式反向拆解，提取 frontmatter 后再与正文拼合
-- 如存在 `{part}/{total}`，按 part 升序排序并校验分片完整
+- 如分片标记中存在 part 和 total 序号，按 part 升序排序并校验分片完整
 - 从评论正文中提取文件内容，去掉隐藏标记、标题和页脚
 - 拼接得到最终文件内容
 
@@ -88,66 +83,20 @@ date "+%Y-%m-%d %H:%M:%S%:z"
 - `status`：`active`
 - `assigned_to`：{当前 AI 代理}
 - `updated_at`：{当前时间}
-- 保留原 `current_step`
-- 在 `## 活动日志` 追加：
-  ```
-  - {YYYY-MM-DD HH:mm:ss±HH:MM} — **Restore Task** by {agent} — Restored task from Issue #{issue-number}
-  ```
-
-### 7. 完成校验
-
-运行完成校验：
-
-```bash
-node .agents/scripts/validate-artifact.js gate restore-task .agents/workspace/active/{task-id} --format text
-```
-
-处理结果：
-- 退出码 0（全部通过）-> 继续到「告知用户」步骤
-- 退出码 1（校验失败）-> 根据输出修复问题后重新运行校验
-- 退出码 2（网络中断）-> 停止执行并告知用户需要人工介入
 
-将校验输出保留在回复中作为当次验证输出。没有当次校验输出，不得声明完成。
+追加 Activity Log，说明任务已从平台 Issue 还原。
 
-### 8. 告知用户
+### 7. 告知用户
 
-> 仅在校验通过后执行本步骤。
-
-> **重要**：以下「下一步」中列出的所有 TUI 命令格式必须完整输出，不要只展示当前 AI 代理对应的格式。如果 `.agents/.airc.json` 中配置了自定义 TUI（`customTUIs`），读取每个工具的 `name` 和 `invoke`，按同样格式补充对应命令行（`${skillName}` 替换为技能名，`${projectName}` 替换为项目名）。
-
-输出格式：
-
-```text
-任务 {task-id} 已从 Issue #{issue-number} 还原。
-
-摘要：
-- 恢复文件：{数量}
-- 任务目录：.agents/workspace/active/{task-id}/
-- 当前步骤：{current_step}
-
-下一步 - 查看任务状态：
-  - Claude Code / OpenCode：/check-task {task-id}
-  - Gemini CLI：/{{project}}:check-task {task-id}
-  - Codex CLI：$check-task {task-id}
-```
+报告已恢复的 task id、恢复文件数量和 active task 目录。
 
 ## 完成检查清单
 
-- [ ] 已获取并解析 Issue 评论
-- [ ] 已还原 `task.md` 和所有可用产物文件
-- [ ] 已更新恢复后的 task.md
-- [ ] 已运行并通过完成校验
-- [ ] 已向用户展示所有 TUI 格式的下一步命令（含自定义 TUI）
-
-## 停止
-
-完成检查清单后立即停止。不要自动继续执行工作流。
+- [ ] 已从平台获取 Issue 评论
+- [ ] 已恢复本地任务文件
+- [ ] 已更新恢复出的任务元数据
+- [ ] 已报告恢复目录
 
-## 错误处理
+### 8. 停止
 
-- Issue 不存在或无权访问
-- 平台 CLI 未认证
-- 找不到带 sync 标记的评论
-- 无法唯一确定 `task-id`
-- 目标目录已存在
-- 分片缺失或顺序不完整
+完成检查清单后立即停止。不要自动提交。

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

@@ -56,7 +56,7 @@ Update task.md and append:
 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
 - Set `status: in-progress` by following issue-sync.md
-- Create or update the `<!-- sync-issue:{task-id}:task -->` comment (follow the task.md comment sync rule in issue-sync.md)
+- Create or update the task comment marker defined in `.agents/rules/issue-sync.md` (follow the task.md comment sync rule in issue-sync.md)
 - Publish the `{review-artifact}` comment
 
 ### 7. Verification Gate

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

@@ -56,7 +56,7 @@ date "+%Y-%m-%d %H:%M:%S%:z"
 如果 task.md 中存在有效的 `issue_number`，执行以下同步操作（任一失败则跳过并继续）：
 - 执行前先读取 `.agents/rules/issue-sync.md`，完成 upstream 仓库检测和权限检测
 - 按 issue-sync.md 设置 `status: in-progress`
-- 创建或更新 `<!-- sync-issue:{task-id}:task -->` 评论（按 issue-sync.md 的 task.md 评论同步规则）
+- 创建或更新 `.agents/rules/issue-sync.md` 中定义的 task 评论标记（按 issue-sync.md 的 task.md 评论同步规则）
 - 发布 `{review-artifact}` 评论
 
 ### 7. 完成校验

package/templates/.agents/skills/review-task/config/verify.json

@@ -36,7 +36,9 @@
       "verify_comment_content": true,
       "verify_task_comment_content": true,
       "verify_issue_type": true,
-      "verify_milestone": true
+      "verify_milestone": true,
+      "expected_status_label_key": "inProgress",
+      "expected_comment_marker_key": "artifact"
     }
   }
 }

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

@@ -21,16 +21,55 @@ Execute the project's full test workflow including compilation checks and unit t
 
 Confirm no compilation errors.
 
-## 2. Run All Unit Tests
+## 2. Run Unit Tests by Layer
+
+This project uses three test layers as an optional optimization; if the test suite is small, all layers may map to the same full test command.
+
+### smoke (target <5s)
+
+```bash
+# TODO: Replace with this project's smoke subset command
+# npm run test:smoke       (Node.js)
+# pytest -m "not slow"     (Python)
+# go test -short ./...     (Go)
+```
+
+Use for:
+- implement-task / refine-task inner loops
+- save-and-run / frequent feedback
+- project structure, configuration, and template contract checks
+
+### core (target <15s)
 
 ```bash
-# TODO: Replace with your project's test command
-# npm test                (Node.js)
-# mvn test                (Maven)
-# pytest                  (Python)
-# go test ./...           (Go)
+# TODO: Replace with this project's core subset command
+# npm run test:core        (Node.js)
+# pytest -m "not contract" (Python)
+# go test ./...            (Go)
 ```
 
+Use for:
+- pre-commit hook (automatic)
+- final verification before writing implementation.md / refinement.md
+- local gate before pushing a PR
+
+### full (complete test suite)
+
+```bash
+# TODO: Replace with this project's full test command
+# npm test                 (Node.js)
+# mvn test                 (Maven)
+# pytest                   (Python)
+# go test ./...            (Go)
+```
+
+Use for:
+- before release / tag
+- CI
+- final gate before merging to main
+
+If the project is not layered yet, smoke / core / full may all map to the same full test command; layering is a feedback-speed optimization, not a prerequisite for using the collaboration workflow.
+
 ## 3. Output Results
 
 Report test result summary:

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

@@ -21,16 +21,55 @@ description: "执行项目完整测试流程"
 
 确认无编译错误。
 
-## 2. 运行所有单元测试
+## 2. 运行单元测试（按层级选择）
+
+本项目把测试分为三层（可选优化）；如果项目测试规模较小，可以全部映射到同一个完整测试命令。
+
+### smoke（目标 <5s）
+
+```bash
+# TODO: 替换为本项目的 smoke 子集命令
+# npm run test:smoke       (Node.js)
+# pytest -m "not slow"     (Python)
+# go test -short ./...     (Go)
+```
+
+适用场景：
+- implement-task / refine-task 内循环
+- 保存即跑 / 频繁反馈
+- 仅断言项目结构、配置、模板契约
+
+### core（目标 <15s）
 
 ```bash
-# TODO: 替换为你的项目测试命令
-# npm test                (Node.js)
-# mvn test                (Maven)
-# pytest                  (Python)
-# go test ./...           (Go)
+# TODO: 替换为本项目的 core 子集命令
+# npm run test:core        (Node.js)
+# pytest -m "not contract" (Python)
+# go test ./...            (Go)
 ```
 
+适用场景：
+- pre-commit hook（自动调用）
+- 写 implementation.md / refinement.md 报告前的最终验证
+- 推送 PR 前的本地把关
+
+### full（完整测试）
+
+```bash
+# TODO: 替换为本项目的完整测试命令
+# npm test                 (Node.js)
+# mvn test                 (Maven)
+# pytest                   (Python)
+# go test ./...            (Go)
+```
+
+适用场景：
+- release / tag 前
+- CI
+- main 合并前的最终把关
+
+如果项目暂不分层，smoke / core / full 可以全部映射到同一个完整测试命令；分层是反馈速度优化项，不是使用协作工作流的前置条件。
+
 ## 3. 输出结果
 
 报告测试结果摘要：

package/templates/.agents/skills/update-agent-infra/SKILL.en.md

@@ -45,6 +45,8 @@ The script outputs JSON to stdout. Parse and record the report.
   list these in the report so users know which files were ignored because a
   built-in template or later external source won
 - `managed.written` / `managed.created`: updated / newly created managed files
+- `managed.removed`: deleted managed files (including old paths removed during template migrations)
+- `managed.skippedPlatform`: managed / merged entries skipped because they belong to a different platform
 - `merged.pending`: list of merged files for AI to process
   - Each item has `target` (project-relative path) and `template` (template-root-relative path)
 - `registryAdded`: newly added file registry entries

package/templates/.agents/skills/update-agent-infra/SKILL.zh-CN.md

@@ -37,6 +37,8 @@ node .agents/skills/update-agent-infra/scripts/sync-templates.js
 - `templateRoot`：模板文件根目录绝对路径
 - `templateSources.conflicts`：外部模板源冲突列表；报告中必须显式展示，说明哪些文件因内置模板或后续外部源获胜而被忽略
 - `managed.written` / `managed.created`：已更新/新建的 managed 文件
+- `managed.removed`：被删除的 managed 文件（包括模板迁移时移除的旧路径）
+- `managed.skippedPlatform`：因归属其他平台而被跳过的 managed / merged 条目
 - `merged.pending`：需要 AI 处理的 merged 文件列表
   - 每项包含 `target`（项目中的目标路径）和 `template`（模板根目录下的相对路径）
 - `registryAdded`：新增的文件注册条目