@fitlab-ai/agent-infra 0.5.6 → 0.5.8

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. 完成校验
 
@@ -100,7 +130,7 @@ node .agents/scripts/validate-artifact.js gate import-issue .agents/workspace/ac
 
 > 仅在校验通过后执行本步骤。
 
-> **重要**：以下「下一步」中列出的所有 TUI 命令格式必须完整输出，不要只展示当前 AI 代理对应的格式。
+> **重要**：以下「下一步」中列出的所有 TUI 命令格式必须完整输出，不要只展示当前 AI 代理对应的格式。如果 `.agents/.airc.json` 中配置了自定义 TUI（`customTUIs`），读取每个工具的 `name` 和 `invoke`，按同样格式补充对应命令行（`${skillName}` 替换为技能名，`${projectName}` 替换为项目名）。
 
 ```
 Issue #{number} 已导入。
@@ -126,8 +156,8 @@ Issue #{number} 已导入。
 - [ ] 更新了 `current_step` 为 requirement-analysis
 - [ ] 更新了 `updated_at` 为当前时间
 - [ ] 追加了 Activity Log 条目到 task.md
-- [ ] 同步了 task 评论到 Issue
-- [ ] 告知了用户下一步（必须展示所有 TUI 的命令格式，不要筛选）
+- [ ] 同步了 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 |
 
@@ -85,7 +85,7 @@ Operational notes:
 
 ### 6. Inform User
 
-> **IMPORTANT**: All TUI command formats listed below must be output in full. Do not show only the format for the current AI agent.
+> **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).
 
 After summarizing the label initialization, show:
 
@@ -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 均需按模块筛选 |
 
@@ -85,7 +85,7 @@ bash .agents/skills/init-labels/scripts/init-labels.sh
 
 ### 6. 告知用户
 
-> **重要**：以下「下一步」中列出的所有 TUI 命令格式必须完整输出，不要只展示当前 AI 代理对应的格式。
+> **重要**：以下「下一步」中列出的所有 TUI 命令格式必须完整输出，不要只展示当前 AI 代理对应的格式。如果 `.agents/.airc.json` 中配置了自定义 TUI（`customTUIs`），读取每个工具的 `name` 和 `invoke`，按同样格式补充对应命令行（`${skillName}` 替换为技能名，`${projectName}` 替换为项目名）。
 
 输出 labels 初始化摘要后，提示：
 
@@ -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-labels/scripts/init-labels.sh

@@ -0,0 +1,6 @@
+#!/bin/sh
+
+set -e
+
+echo "Label initialization skipped: this code platform does not provide a built-in label adapter." >&2
+exit 0

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
 
@@ -62,7 +62,7 @@ Operational notes:
 
 ### 5. Inform User
 
-> **IMPORTANT**: All TUI command formats listed below must be output in full. Do not show only the format for the current AI agent.
+> **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).
 
 After summarizing the milestone initialization, show:
 
@@ -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 体系。
 
 ## 执行流程
 
@@ -62,7 +62,7 @@ bash .agents/skills/init-milestones/scripts/init-milestones.sh "$ARGUMENTS"
 
 ### 5. 告知用户
 
-> **重要**：以下「下一步」中列出的所有 TUI 命令格式必须完整输出，不要只展示当前 AI 代理对应的格式。
+> **重要**：以下「下一步」中列出的所有 TUI 命令格式必须完整输出，不要只展示当前 AI 代理对应的格式。如果 `.agents/.airc.json` 中配置了自定义 TUI（`customTUIs`），读取每个工具的 `name` 和 `invoke`，按同样格式补充对应命令行（`${skillName}` 替换为技能名，`${projectName}` 替换为项目名）。
 
 输出 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/init-milestones/scripts/init-milestones.sh

@@ -0,0 +1,6 @@
+#!/bin/sh
+
+set -e
+
+echo "Milestone initialization skipped: this code platform does not provide a built-in milestone adapter." >&2
+exit 0

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
@@ -121,7 +121,7 @@ Keep the gate output in your reply as fresh evidence. Do not claim completion wi
 
 > 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.
+> **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:
 ```
@@ -157,7 +157,7 @@ Next step - implement the task:
 - [ ] Marked technical-design as complete in workflow progress
 - [ ] Appended an Activity Log entry to task.md
 - [ ] Informed the user that this is a human review checkpoint
-- [ ] Informed the user of the next step (must include all TUI command formats; do not filter)
+- [ ] Informed the user of the next step (must include all TUI command formats, including any custom TUIs; do not filter)
 
 ## STOP
 

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. 完成校验
@@ -121,7 +121,7 @@ node .agents/scripts/validate-artifact.js gate plan-task .agents/workspace/activ
 
 > 仅在校验通过后执行本步骤。
 
-> **重要**：以下「下一步」中列出的所有 TUI 命令格式必须完整输出，不要只展示当前 AI 代理对应的格式。
+> **重要**：以下「下一步」中列出的所有 TUI 命令格式必须完整输出，不要只展示当前 AI 代理对应的格式。如果 `.agents/.airc.json` 中配置了自定义 TUI（`customTUIs`），读取每个工具的 `name` 和 `invoke`，按同样格式补充对应命令行（`${skillName}` 替换为技能名，`${projectName}` 替换为项目名）。
 
 输出格式：
 ```
@@ -157,7 +157,7 @@ node .agents/scripts/validate-artifact.js gate plan-task .agents/workspace/activ
 - [ ] 在工作流进度中标记了 technical-design 为已完成
 - [ ] 追加了 Activity Log 条目到 task.md
 - [ ] 告知了用户这是人工审查检查点
-- [ ] 告知了用户下一步（必须展示所有 TUI 的命令格式，不要筛选）
+- [ ] 告知了用户下一步（必须展示所有 TUI 的命令格式，含自定义 TUI，不要筛选）
 
 ## 停止
 

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/post-release/SKILL.en.md

@@ -0,0 +1,95 @@
+---
+name: post-release
+description: "Run post-release follow-up tasks"
+---
+
+# Post-release Tasks
+
+Run the standard follow-up workflow after a release tag has been pushed.
+
+## Execution Flow
+
+### 1. Detect the Latest Released Version
+
+```bash
+git tag --sort=-v:refname | grep -E '^v[0-9]+\.[0-9]+\.[0-9]+$' | head -n 1
+```
+
+- Detect the latest `vX.Y.Z` tag, then strip the `v` prefix when you need the version number in later steps
+- If no tag is found, error: "No released version tag found. Please create and push a release tag first."
+
+### 2. Verify Clean Workspace
+
+```bash
+git status --short
+```
+
+- If there are uncommitted changes, error: "Workspace has uncommitted changes. Please commit or stash first."
+
+### 3. Prepare the Next Development Version
+
+<!-- TODO: Replace this step with your project's version bump command -->
+
+```bash
+# TODO: Replace with your project's post-release version bump command
+# npm version prerelease --preid=alpha --no-git-tag-version
+```
+
+- Update lockfiles or generated version metadata if your project needs them
+- Keep all version references in sync after the bump
+
+### 4. Rebuild Generated Artifacts
+
+<!-- TODO: Replace this step with your project's rebuild command -->
+
+```bash
+# TODO: Replace with your project's artifact rebuild command
+```
+
+- Rebuild any generated files, embedded assets, or inline templates affected by the new version
+- If your project has no generated artifacts, remove this step in the project-specific copy
+
+### 5. Run Other Post-release Tasks (Optional)
+
+<!-- TODO: Add project-specific follow-up tasks such as demo capture, docs publishing, or downstream notifications -->
+
+- Examples: record a terminal demo, refresh a docs site, notify downstream teams, update release dashboards
+- If there are no extra tasks, remove this step in the project-specific copy
+
+### 6. Create the Follow-up Commit
+
+```bash
+git add -A
+git commit -m "chore: prepare next dev iteration after v{released-version}"
+```
+
+### 7. Output Summary
+
+> **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).
+
+```
+Post-release tasks completed.
+
+Summary:
+- Released version: {released-version}
+- Next development version: {new-version}
+- Extra tasks completed: {summary}
+
+Next step (manual):
+- Push branch: git push origin {current-branch}
+```
+
+## Notes
+
+1. **No arguments**: Detect the released version from the latest tag instead of asking the user to repeat it
+2. **Clean workspace required**: Avoid mixing unrelated edits into the post-release commit
+3. **Project-specific customization**: Replace the TODO steps with the commands your project actually needs
+4. **Local-only workflow**: This skill prepares local changes and does not push automatically
+
+## Error Handling
+
+- No release tag found: Prompt the user to finish the release first
+- Dirty workspace: Prompt the user to commit or stash changes
+- Version bump failed: Display the command error and stop
+- Artifact rebuild failed: Display the build error and stop
+- Git commit failed: Display the error and leave the workspace intact for manual recovery

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

@@ -0,0 +1,95 @@
+---
+name: post-release
+description: "执行版本发布后的后处理工作"
+---
+
+# 发布后处理
+
+在版本标签推送完成后，执行标准化的发布后收尾流程。
+
+## 执行流程
+
+### 1. 检测最新发布版本
+
+```bash
+git tag --sort=-v:refname | grep -E '^v[0-9]+\.[0-9]+\.[0-9]+$' | head -n 1
+```
+
+- 检测最新 `vX.Y.Z` 标签，并在后续步骤中去除 `v` 前缀得到版本号
+- 如果没有找到标签，报错："No released version tag found. Please create and push a release tag first."
+
+### 2. 验证工作区干净
+
+```bash
+git status --short
+```
+
+- 如果存在未提交变更，报错："Workspace has uncommitted changes. Please commit or stash first."
+
+### 3. 准备下一个开发版本
+
+<!-- TODO: 将此步骤替换为你的项目版本 bump 命令 -->
+
+```bash
+# TODO: 替换为你的项目发布后版本 bump 命令
+# npm version prerelease --preid=alpha --no-git-tag-version
+```
+
+- 如果项目需要，记得同步锁文件或其他版本元数据
+- 版本 bump 后保持所有版本引用一致
+
+### 4. 重新生成构建产物
+
+<!-- TODO: 将此步骤替换为你的项目产物重建命令 -->
+
+```bash
+# TODO: 替换为你的项目产物重建命令
+```
+
+- 重建所有受新版本号影响的生成文件、内嵌产物或内联模板
+- 如果项目没有生成产物，请在项目特化版本中删除此步骤
+
+### 5. 执行其他发布后任务（可选）
+
+<!-- TODO: 添加项目特定的发布后任务，例如录制演示、发布文档站或通知下游 -->
+
+- 示例：录制终端演示、刷新文档站、通知下游团队、更新发布面板
+- 如果没有额外任务，请在项目特化版本中删除此步骤
+
+### 6. 创建后处理提交
+
+```bash
+git add -A
+git commit -m "chore: prepare next dev iteration after v{released-version}"
+```
+
+### 7. 输出摘要
+
+> **重要**：以下「下一步」中列出的所有 TUI 命令格式必须完整输出，不要只展示当前 AI 代理对应的格式。如果 `.agents/.airc.json` 中配置了自定义 TUI（`customTUIs`），读取每个工具的 `name` 和 `invoke`，按同样格式补充对应命令行（`${skillName}` 替换为技能名，`${projectName}` 替换为项目名）。
+
+```
+发布后处理已完成。
+
+结果摘要：
+- 已发布版本：{released-version}
+- 新开发版本：{new-version}
+- 额外任务完成情况：{summary}
+
+下一步（手动执行）：
+- 推送分支：git push origin {current-branch}
+```
+
+## 注意事项
+
+1. **无参数设计**：从最新标签自动检测已发布版本，不要求用户重复输入
+2. **需要干净工作区**：避免把无关改动带入发布后提交
+3. **项目定制**：将带 TODO 的步骤替换为你的项目实际命令
+4. **仅本地执行**：本技能只准备本地变更，不自动推送
+
+## 错误处理
+
+- 未找到发布标签：提示用户先完成发布
+- 工作区不干净：提示先提交或暂存
+- 版本 bump 失败：显示命令错误并停止
+- 产物重建失败：显示构建错误并停止
+- Git 提交失败：显示错误并保留当前工作区供人工处理

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
@@ -84,7 +84,7 @@ Keep the gate output in your reply as fresh evidence. Do not claim completion wi
 
 > 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.
+> **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).
 
 After summarizing the fixes, present the next step:
 

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. 完成校验
@@ -84,7 +84,7 @@ node .agents/scripts/validate-artifact.js gate refine-task .agents/workspace/act
 
 > 仅在校验通过后执行本步骤。
 
-> **重要**：以下「下一步」中列出的所有 TUI 命令格式必须完整输出，不要只展示当前 AI 代理对应的格式。
+> **重要**：以下「下一步」中列出的所有 TUI 命令格式必须完整输出，不要只展示当前 AI 代理对应的格式。如果 `.agents/.airc.json` 中配置了自定义 TUI（`customTUIs`），读取每个工具的 `name` 和 `invoke`，按同样格式补充对应命令行（`${skillName}` 替换为技能名，`${projectName}` 替换为项目名）。
 
 输出修复摘要后，展示下一步：
 

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-title/SKILL.en.md

@@ -62,7 +62,7 @@ Title changes require write permission. Follow the permission-degradation rules
 
 ### 5. Inform User
 
-> **IMPORTANT**: All TUI command formats listed below must be output in full. Do not show only the format for the current AI agent.
+> **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).
 
 If the skill updated an Issue title, explain that no extra sync command is required; continue with the workflow skill that matches the task's current stage.
 

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

@@ -62,7 +62,7 @@ Issue/PR #{id} 分析结果：
 
 ### 5. 告知用户
 
-> **重要**：以下「下一步」中列出的所有 TUI 命令格式必须完整输出，不要只展示当前 AI 代理对应的格式。
+> **重要**：以下「下一步」中列出的所有 TUI 命令格式必须完整输出，不要只展示当前 AI 代理对应的格式。如果 `.agents/.airc.json` 中配置了自定义 TUI（`customTUIs`），读取每个工具的 `name` 和 `invoke`，按同样格式补充对应命令行（`${skillName}` 替换为技能名，`${projectName}` 替换为项目名）。
 
 如果修改了 Issue 标题，提示无需额外同步命令；后续按任务当前阶段继续执行对应工作流技能。