@fitlab-ai/agent-infra 0.5.7 → 0.5.8

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

@@ -137,7 +137,7 @@ Next step - run requirements analysis:
   - Gemini CLI: /{{project}}:analyze-task {task-id}
   - Codex CLI: $analyze-task {task-id}
 
-Or create a GitHub Issue first:
+Or create an Issue first:
   - Claude Code / OpenCode: /create-issue {task-id}
   - Gemini CLI: /{{project}}:create-issue {task-id}
   - Codex CLI: $create-issue {task-id}
@@ -161,8 +161,8 @@ Wait for the user to run the `analyze-task` skill.
 ## Notes
 
 1. **Clarity**: if the user description is vague or missing key information, ask for clarification first
-2. **Difference from `import-issue`**: `import-issue` imports from a GitHub Issue; `create-task` creates from a free-form description
-3. **Workflow order**: after creating a task, typically run `analyze-task` before `plan-task`; if you need GitHub tracking first, you may run `create-issue` first
+2. **Difference from `import-issue`**: `import-issue` imports from an Issue; `create-task` creates from a free-form description
+3. **Workflow order**: after creating a task, typically run `analyze-task` before `plan-task`; if you need platform tracking first, you may run `create-issue` first
 
 ## Error Handling
 

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

@@ -137,7 +137,7 @@ node .agents/scripts/validate-artifact.js gate create-task .agents/workspace/act
   - Gemini CLI：/agent-infra:analyze-task {task-id}
   - Codex CLI：$analyze-task {task-id}
 
-或先创建 GitHub Issue：
+或先创建 Issue：
   - Claude Code / OpenCode：/create-issue {task-id}
   - Gemini CLI：/agent-infra:create-issue {task-id}
   - Codex CLI：$create-issue {task-id}
@@ -161,8 +161,8 @@ node .agents/scripts/validate-artifact.js gate create-task .agents/workspace/act
 ## 注意事项
 
 1. **清晰度**：如果用户描述模糊或缺少关键信息，先要求澄清
-2. **与 import-issue 的区别**：`import-issue` 从 GitHub Issue 导入任务；`create-task` 从自由描述创建
-3. **工作流顺序**：创建任务后，通常先执行 `analyze-task` 再进入 `plan-task`；如需先建立 GitHub 跟踪，也可先执行 `create-issue`
+2. **与 import-issue 的区别**：`import-issue` 从 Issue 导入任务；`create-task` 从自由描述创建
+3. **工作流顺序**：创建任务后，通常先执行 `analyze-task` 再进入 `plan-task`；如需先建立 平台跟踪，也可先执行 `create-issue`
 
 ## 错误处理
 

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

@@ -95,7 +95,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` first 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 `{implementation-artifact}` comment
 
 ### 10. Verification Gate

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

@@ -95,7 +95,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 评论同步规则）
 - 发布 `{implementation-artifact}` 评论
 
 ### 10. 完成校验

package/templates/.agents/skills/implement-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/import-codescan/SKILL.en.md

@@ -25,7 +25,7 @@ Extract key information:
 - `rule`: rule information (`id`, `severity`, `description`, `security_severity_level`)
 - `tool`: scanning tool information (`name`, `version`)
 - `most_recent_instance`: location (`path`, `start_line`, `end_line`) and message
-- `html_url`: GitHub alert link
+- `html_url`: alert link in the platform
 
 ### 2. Create the Task Directory and File
 

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

@@ -25,7 +25,7 @@ description: "导入 Code Scanning 告警并创建修复任务"
 - `rule`：规则信息（id、severity、description、security_severity_level）
 - `tool`：扫描工具信息（name、version）
 - `most_recent_instance`：位置（path、start_line、end_line）、消息
-- `html_url`：GitHub 告警链接
+- `html_url`：平台告警链接
 
 ### 2. 创建任务目录和文件
 

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

@@ -1,11 +1,11 @@
 ---
 name: import-issue
-description: "Import a GitHub Issue and create a task"
+description: "Import an Issue and create a task"
 ---
 
 # Import Issue
 
-Import the specified GitHub Issue and create a task. Argument: issue number.
+Import the specified Issue and create a task. Argument: issue number.
 
 ## Boundary / Critical Rules
 
@@ -24,22 +24,46 @@ Use the Issue title as-is for the task title (preserve the Issue's original lang
 
 ### 2. Check for an Existing Task
 
-Search `.agents/workspace/active/` for an existing task linked to this Issue.
+2.1 Search `.agents/workspace/active/` for an existing task linked to this Issue.
 - If found, ask the user whether to re-import or continue with the existing task
-- If not found, create a new task
+- If not found, continue to 2.2
+
+2.2 Scan Issue comments for sync markers and look for a recoverable historical task ID:
+
+If `$upstream_repo` was not set in step 1, omit `--repo`; the script will infer it using the issue-sync.md detection rule.
+
+```bash
+node .agents/scripts/platform-adapters/find-existing-task.js --issue <issue-number> --repo "$upstream_repo" --format json
+```
+
+- Script outputs `found=false`: create a new task through the normal import flow
+- Script outputs `found=true`: reuse `task_id`
+- Script exits 2: treat it as network, authentication, or platform API degradation; show the failure reason from script stderr to the user, then continue with the new-task import flow without blocking
 
 ### 3. Create the Task Directory and File
 
+3.1 Decide the task ID and `created_at`.
+
+| Scenario | Trigger | task ID source | created_at source | User confirmation |
+|---|---|---|---|---|
+| Scenario A | 2.1 finds a local task | Reuse local ID | Preserve local value | Must ask whether to re-import or continue using the existing task |
+| Scenario B | 2.1 no match + 2.2 no candidate | Create with `date +%Y%m%d-%H%M%S` | Current time | Not required |
+| Scenario C | 2.1 no match + 2.2 any candidate | Automatically reuse the earliest candidate ID | Prefer remote frontmatter `created_at`; use current time if missing | Inform only |
+
 ```bash
 date +%Y%m%d-%H%M%S
 ```
 
-- Create the directory: `.agents/workspace/active/TASK-{yyyyMMdd-HHmmss}/`
+3.2 Write the task directory and `task.md`.
+
+- 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
+- Always write `current_step` as `requirement-analysis`; do not restore the remote original `current_step`
 
 Task metadata:
 ```yaml
-id: TASK-{yyyyMMdd-HHmmss}
+id: {task-id}
 issue_number: <issue-number>
 type: feature|bugfix|refactor|docs|chore
 branch: <project>-<type>-<slug>
@@ -52,6 +76,11 @@ current_step: requirement-analysis
 assigned_to: {current AI agent}
 ```
 
+3.3 Append Activity Log entries.
+
+- Scenario B: append `Import Issue`
+- Scenario C: append `Import Issue (Recovered)` and include the recovered task ID, any recoverable original `current_step`, original `assigned_to`, and that `current_step` was reset to `requirement-analysis`; if some frontmatter fields are missing or damaged, mention the fallback in the same entry
+
 ### 4. Update Task Status
 
 Get the current time:
@@ -69,6 +98,7 @@ Update `.agents/workspace/active/{task-id}/task.md`:
   ```
   - {YYYY-MM-DD HH:mm:ss±HH:MM} — **Import Issue** by {agent} — Issue #{number} imported
   ```
+  If step 3.3 already appended recovery Activity Log entries, do not append a duplicate equivalent entry.
 
 ### 5. Assign the Issue Assignee
 
@@ -79,7 +109,7 @@ If task.md contains a valid `issue_number`, use the Issue update command from `.
 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
 - Check the Issue's current milestone; if it is unset, read `.agents/rules/milestone-inference.md` and infer plus set the milestone using "Stage 1: `create-issue`". If `has_triage=false` or the inference is uncertain, skip and continue
-- Create or update the `<!-- sync-issue:{task-id}:task -->` comment (follow the task.md comment sync rule in issue-sync.md)
+- After every scenario, task comment sync is mandatory: create or update the task comment marker defined in `.agents/rules/issue-sync.md` so the remote `:task` comment exists and matches the local `task.md` content (follow the task.md comment sync rule in issue-sync.md)
 
 ### 7. Verification Gate
 
@@ -126,7 +156,7 @@ Next step - run requirements analysis:
 - [ ] Updated `current_step` to requirement-analysis
 - [ ] Updated `updated_at` to the current time
 - [ ] Appended an Activity Log entry to task.md
-- [ ] Synced the task comment to the Issue
+- [ ] Synced the task comment to the Issue, with remote content matching local task.md
 - [ ] Informed the user of the next step (must include all TUI command formats, including any custom TUIs; do not filter)
 - [ ] **Did not modify any business code**
 
@@ -143,5 +173,5 @@ After completing the checklist, **stop immediately**. Do not continue to later s
 ## Error Handling
 
 - Issue not found: output "Issue #{number} not found, please check the issue number"
-- Network error: output "Cannot connect to GitHub, please check network"
+- Network error: output "Cannot connect to the platform, please check network"
 - Permission error: output "No access to this repository"

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

@@ -1,11 +1,11 @@
 ---
 name: import-issue
-description: "从 GitHub Issue 导入并创建任务"
+description: "从 Issue 导入并创建任务"
 ---
 
 # 导入 Issue
 
-导入指定的 GitHub Issue 并创建任务。参数：issue 编号。
+导入指定的 Issue 并创建任务。参数：issue 编号。
 
 ## 行为边界 / 关键规则
 
@@ -24,22 +24,46 @@ description: "从 GitHub Issue 导入并创建任务"
 
 ### 2. 检查已有任务
 
-搜索 `.agents/workspace/active/` 中是否已有链接到此 Issue 的任务。
+2.1 搜索 `.agents/workspace/active/` 中是否已有链接到此 Issue 的任务。
 - 如果找到，询问用户是重新导入还是继续使用现有任务
-- 如果未找到，创建新任务
+- 如果未找到，继续执行 2.2
+
+2.2 扫描 Issue 评论中的同步标记，查找可恢复的历史任务 ID：
+
+如未在步骤 1 中已设置 `$upstream_repo`，可省略 `--repo`，脚本会自动按 issue-sync.md 的检测规则推断。
+
+```bash
+node .agents/scripts/platform-adapters/find-existing-task.js --issue <issue-number> --repo "$upstream_repo" --format json
+```
+
+- 脚本输出 `found=false`：按新 Issue 导入流程创建新任务
+- 脚本输出 `found=true`：复用 `task_id`
+- 脚本退出码 2：视为网络、认证或 platform API 降级，向用户展示脚本 stderr 中的失败原因后，按新 Issue 导入流程继续，不阻塞导入
 
 ### 3. 创建任务目录和文件
 
+3.1 决定 task ID 和 `created_at`。
+
+| 场景 | 触发条件 | task ID 来源 | created_at 来源 | 用户确认 |
+|---|---|---|---|---|
+| 场景 A | 2.1 命中本地任务 | 复用本地 ID | 本地保留 | 必须询问"重新导入还是继续使用现有任务" |
+| 场景 B | 2.1 无命中 + 2.2 无候选 | `date +%Y%m%d-%H%M%S` 新建 | 当前时间 | 不需要 |
+| 场景 C | 2.1 无命中 + 2.2 有候选 | 自动复用最早候选 ID | 优先用远端 frontmatter 的 `created_at`，缺失时用当前时间 | 告知即可 |
+
 ```bash
 date +%Y%m%d-%H%M%S
 ```
 
-- 创建目录：`.agents/workspace/active/TASK-{yyyyMMdd-HHmmss}/`
+3.2 写入任务目录和 `task.md`。
+
+- 创建目录：`.agents/workspace/active/{task-id}/`
 - 使用 `.agents/templates/task.md` 模板创建 `task.md`
+- 场景 C 优先沿用远端 frontmatter 中的 `type`、`workflow`、`branch`、`created_by`、`milestone`；缺失或损坏字段按 Issue 标签和当前规则重新推断
+- `current_step` 始终写入 `requirement-analysis`，不要恢复为远端原 `current_step`
 
 任务元数据：
 ```yaml
-id: TASK-{yyyyMMdd-HHmmss}
+id: {task-id}
 issue_number: <issue-number>
 type: feature|bugfix|refactor|docs|chore
 branch: <project>-<type>-<slug>
@@ -52,6 +76,11 @@ current_step: requirement-analysis
 assigned_to: {当前 AI 代理}
 ```
 
+3.3 追加 Activity Log。
+
+- 场景 B：追加 `Import Issue`
+- 场景 C：追加 `Import Issue (Recovered)`，注明恢复的 task ID、可恢复的原 `current_step`、原 `assigned_to`，并说明 `current_step` 已重置为 `requirement-analysis`；如果部分 frontmatter 字段缺失或损坏，在同一条记录中注明 fallback
+
 ### 4. 更新任务状态
 
 获取当前时间：
@@ -69,6 +98,7 @@ date "+%Y-%m-%d %H:%M:%S%:z"
   ```
   - {YYYY-MM-DD HH:mm:ss±HH:MM} — **Import Issue** by {agent} — Issue #{number} imported
   ```
+  如果步骤 3.3 已经按恢复场景追加了 Activity Log，不要重复追加同义记录。
 
 ### 5. 分配 Issue Assignee
 
@@ -79,7 +109,7 @@ date "+%Y-%m-%d %H:%M:%S%:z"
 如果 task.md 中存在有效的 `issue_number`，执行以下同步操作（任一失败则跳过并继续）：
 - 执行前先读取 `.agents/rules/issue-sync.md`，完成 upstream 仓库检测和权限检测
 - 检查 Issue 当前 milestone；如果未设置，先读取 `.agents/rules/milestone-inference.md`，按其中的「阶段 1：`create-issue`」规则推断并设置 milestone；如果 `has_triage=false` 或推断不确定，跳过并继续
-- 创建或更新 `<!-- sync-issue:{task-id}:task -->` 评论（按 issue-sync.md 的 task.md 评论同步规则）
+- 所有场景结束后，必须执行一次 task 留言同步，创建或更新 `.agents/rules/issue-sync.md` 中定义的 task 评论标记，确保远端 `:task` 评论存在且内容与本地 `task.md` 一致（按 issue-sync.md 的 task.md 评论同步规则）
 
 ### 7. 完成校验
 
@@ -126,7 +156,7 @@ Issue #{number} 已导入。
 - [ ] 更新了 `current_step` 为 requirement-analysis
 - [ ] 更新了 `updated_at` 为当前时间
 - [ ] 追加了 Activity Log 条目到 task.md
-- [ ] 同步了 task 评论到 Issue
+- [ ] 同步了 task 评论到 Issue，且远端内容与本地 task.md 一致
 - [ ] 告知了用户下一步（必须展示所有 TUI 的命令格式，含自定义 TUI，不要筛选）
 - [ ] **没有修改任何业务代码**
 
@@ -143,5 +173,5 @@ Issue #{number} 已导入。
 ## 错误处理
 
 - Issue 未找到：提示 "Issue #{number} not found, please check the issue number"
-- 网络错误：提示 "Cannot connect to GitHub, please check network"
+- 网络错误：提示 "Cannot connect to the platform, please check network"
 - 权限错误：提示 "No access to this repository"

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

@@ -1,11 +1,11 @@
 ---
 name: init-labels
-description: "Initialize the repository's standard GitHub Labels taxonomy"
+description: "Initialize the repository's standard labels taxonomy"
 ---
 
-# Initialize GitHub Labels
+# Initialize labels
 
-Initialize the repository's standard GitHub Labels taxonomy.
+Initialize the repository's standard labels taxonomy.
 
 ## Execution Flow
 
@@ -36,14 +36,14 @@ The script and `.agents/rules/label-milestone-setup.md` are responsible for:
 The script manages these common label families:
 - `type:` labels such as `type: bug`, `type: enhancement`, `type: feature`, `type: documentation`, `type: dependency-upgrade`, and `type: task`
 - `status:` labels such as `status: waiting-for-triage`, `status: in-progress`, and `status: waiting-for-internal-feedback`
-- GitHub-default-name labels intentionally overwritten in place: `good first issue` and `help wanted`
+- platform-default-name labels intentionally overwritten in place: `good first issue` and `help wanted`
 - Additional shared labels such as `dependencies`
 
 #### Scope
 
 | Label prefix | Issue | PR | Notes |
 |---|---|---|---|
-| `type:` | — | Yes | Issues use the native GitHub Type field; PRs need `type:` labels to drive changelog grouping |
+| `type:` | — | Yes | Issues use the native platform Type field; PRs need `type:` labels to drive changelog grouping |
 | `status:` | Yes | — | PRs already have their own state flow (Open/Draft/Merged/Closed); Issues use `status:` labels for project tracking |
 | `in:` | Yes | Yes | Both Issues and PRs need module-based filtering |
 
@@ -98,8 +98,8 @@ Next step - initialize milestones (optional):
 
 ## Error Handling
 
-- `gh` not found: prompt "GitHub CLI (`gh`) is not installed"
-- Authentication failed: prompt "GitHub CLI is not authenticated"
-- Repository access failed: prompt "Unable to access the current repository with gh"
+- platform CLI not found: prompt "the platform CLI is not installed"
+- Authentication failed: prompt "the platform CLI is not authenticated"
+- Repository access failed: prompt "Unable to access the current repository with the platform CLI"
 - Permission error: prompt "No permission to manage labels in this repository"
-- API rate limit: prompt "GitHub API rate limit reached, please retry later"
+- API rate limit: prompt "platform API rate limit reached, please retry later"

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

@@ -1,11 +1,11 @@
 ---
 name: init-labels
-description: "初始化仓库的 GitHub Labels 体系"
+description: "初始化仓库的 labels 体系"
 ---
 
-# 初始化 GitHub Labels
+# 初始化 labels
 
-一次性初始化仓库的标准 GitHub Labels 体系。
+一次性初始化仓库的标准 labels 体系。
 
 ## 执行流程
 
@@ -36,14 +36,14 @@ bash .agents/skills/init-labels/scripts/init-labels.sh
 脚本管理以下通用 label 族：
 - `type:` labels，例如 `type: bug`、`type: enhancement`、`type: feature`、`type: documentation`、`type: dependency-upgrade`、`type: task`
 - `status:` labels，例如 `status: waiting-for-triage`、`status: in-progress`、`status: waiting-for-internal-feedback`
-- 明确覆盖的 GitHub 默认同名 labels：`good first issue` 和 `help wanted`
+- 明确覆盖的 平台默认同名 labels：`good first issue` 和 `help wanted`
 - 额外通用 labels，例如 `dependencies`
 
 #### 适用范围
 
 | Label 前缀 | Issue | PR | 说明 |
 |---|---|---|---|
-| `type:` | — | Yes | Issue 使用 GitHub 原生 Type 字段；PR 无原生类型字段，需 `type:` label 驱动 changelog |
+| `type:` | — | Yes | Issue 使用 平台原生 Type 字段；PR 无原生类型字段，需 `type:` label 驱动 changelog |
 | `status:` | Yes | — | PR 有自身状态流转（Open/Draft/Merged/Closed）；Issue 使用 `status:` label 标记项目管理状态 |
 | `in:` | Yes | Yes | Issue 和 PR 均需按模块筛选 |
 
@@ -98,8 +98,8 @@ bash .agents/skills/init-labels/scripts/init-labels.sh
 
 ## 错误处理
 
-- 未找到 `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"
 - 权限不足：提示 "No permission to manage labels 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/init-milestones/SKILL.en.md

@@ -1,11 +1,11 @@
 ---
 name: init-milestones
-description: "Initialize the repository's standard GitHub Milestones taxonomy"
+description: "Initialize the repository's standard milestones taxonomy"
 ---
 
-# Initialize GitHub Milestones
+# Initialize milestones
 
-Initialize the repository's standard GitHub Milestones taxonomy.
+Initialize the repository's standard milestones taxonomy.
 
 ## Execution Flow
 
@@ -75,10 +75,10 @@ Next step - initialize labels (optional):
 
 ## Error Handling
 
-- `gh` not found: prompt "GitHub CLI (`gh`) is not installed"
-- Authentication failed: prompt "GitHub CLI is not authenticated"
-- Repository access failed: prompt "Unable to access the current repository with gh"
+- platform CLI not found: prompt "the platform CLI is not installed"
+- Authentication failed: prompt "the platform CLI is not authenticated"
+- Repository access failed: prompt "Unable to access the current repository with the platform CLI"
 - Version detection failed: prompt "Unable to determine current version baseline"
 - No `v*` tags found in `--history` mode: prompt "No history tags found matching v*; only standard milestones will be created"
 - Permission error: prompt "No permission to manage milestones in this repository"
-- API rate limit: prompt "GitHub API rate limit reached, please retry later"
+- API rate limit: prompt "platform API rate limit reached, please retry later"

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/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.