@fitlab-ai/agent-infra 0.5.1 → 0.5.3

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

@@ -17,9 +17,7 @@ description: "导入 Dependabot 安全告警并创建修复任务"
 
 ### 1. 获取告警信息
 
-```bash
-gh api repos/{owner}/{repo}/dependabot/alerts/<alert-number>
-```
+执行前先读取 `.agents/rules/security-alerts.md`，并按其中的 Dependabot 告警读取命令获取告警详情。
 
 提取关键信息：
 - `number`：告警编号
@@ -50,13 +48,13 @@ ghsa_id: <GHSA-ID>
 获取当前时间：
 
 ```bash
-date "+%Y-%m-%d %H:%M:%S"
+date "+%Y-%m-%d %H:%M:%S%:z"
 ```
 
 更新 task.md：`current_step` -> `requirement-analysis`。
 - **追加**到 `## Activity Log`（不要覆盖之前的记录）：
   ```
-  - {yyyy-MM-dd HH:mm:ss} — **Import Dependabot Alert** by {agent} — Dependabot alert #{alert-number} imported
+  - {YYYY-MM-DD HH:mm:ss±HH:MM} — **Import Dependabot Alert** by {agent} — Dependabot alert #{alert-number} imported
   ```
 
 ### 4. 完成校验

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

@@ -17,9 +17,7 @@ Import the specified GitHub Issue and create a task. Argument: issue number.
 
 ### 1. Retrieve Issue Information
 
-```bash
-gh issue view <issue-number> --json number,title,body,labels
-```
+Read `.agents/rules/issue-pr-commands.md` first, then use its "Read an Issue" command to load the Issue data.
 
 Extract: issue number, title, description, and labels.
 Use the Issue title as-is for the task title (preserve the Issue's original language).
@@ -47,8 +45,8 @@ type: feature|bugfix|refactor|docs|chore
 branch: <project>-<type>-<slug>
 workflow: feature-development|bug-fix|refactoring
 status: active
-created_at: {yyyy-MM-dd HH:mm:ss}
-updated_at: {yyyy-MM-dd HH:mm:ss}
+created_at: {YYYY-MM-DD HH:mm:ss±HH:MM}
+updated_at: {YYYY-MM-DD HH:mm:ss±HH:MM}
 created_by: human
 current_step: requirement-analysis
 assigned_to: {current AI agent}
@@ -59,7 +57,7 @@ assigned_to: {current AI agent}
 Get the current time:
 
 ```bash
-date "+%Y-%m-%d %H:%M:%S"
+date "+%Y-%m-%d %H:%M:%S%:z"
 ```
 
 Update `.agents/workspace/active/{task-id}/task.md`:
@@ -69,18 +67,12 @@ Update `.agents/workspace/active/{task-id}/task.md`:
 - `## Context` -> `- **Branch**:`: update it to the generated branch name
 - **Append** to `## Activity Log` (do NOT overwrite previous entries):
   ```
-  - {yyyy-MM-dd HH:mm:ss} — **Import Issue** by {agent} — Issue #{number} imported
+  - {YYYY-MM-DD HH:mm:ss±HH:MM} — **Import Issue** by {agent} — Issue #{number} imported
   ```
 
 ### 5. Assign the Issue Assignee
 
-If task.md contains a valid `issue_number`, assign the Issue to the current executor:
-
-```bash
-gh issue edit {issue-number} --add-assignee @me 2>/dev/null || true
-```
-
-See the Assignee Sync rules in `.agents/rules/issue-sync.md`.
+If task.md contains a valid `issue_number`, use the Issue update command from `.agents/rules/issue-pr-commands.md` to add the current executor as an assignee. The behavioral boundary still follows `.agents/rules/issue-sync.md`.
 
 ### 6. Verification Gate
 

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

@@ -17,9 +17,7 @@ description: "从 GitHub Issue 导入并创建任务"
 
 ### 1. 获取 Issue 信息
 
-```bash
-gh issue view <issue-number> --json number,title,body,labels
-```
+执行前先读取 `.agents/rules/issue-pr-commands.md`，并按其中的 “读取 Issue” 命令获取 Issue 信息。
 
 提取：issue 编号、标题、描述、标签。
 任务标题直接使用 Issue 的原始标题（保持 Issue 标题的原始语言）。
@@ -47,8 +45,8 @@ type: feature|bugfix|refactor|docs|chore
 branch: <project>-<type>-<slug>
 workflow: feature-development|bug-fix|refactoring
 status: active
-created_at: {yyyy-MM-dd HH:mm:ss}
-updated_at: {yyyy-MM-dd HH:mm:ss}
+created_at: {YYYY-MM-DD HH:mm:ss±HH:MM}
+updated_at: {YYYY-MM-DD HH:mm:ss±HH:MM}
 created_by: human
 current_step: requirement-analysis
 assigned_to: {当前 AI 代理}
@@ -59,7 +57,7 @@ assigned_to: {当前 AI 代理}
 获取当前时间：
 
 ```bash
-date "+%Y-%m-%d %H:%M:%S"
+date "+%Y-%m-%d %H:%M:%S%:z"
 ```
 
 更新 `.agents/workspace/active/{task-id}/task.md`：
@@ -69,18 +67,12 @@ date "+%Y-%m-%d %H:%M:%S"
 - `## 上下文` 中的 `- **分支**：`：更新为生成的分支名
 - **追加**到 `## Activity Log`（不要覆盖之前的记录）：
   ```
-  - {yyyy-MM-dd HH:mm:ss} — **Import Issue** by {agent} — Issue #{number} imported
+  - {YYYY-MM-DD HH:mm:ss±HH:MM} — **Import Issue** by {agent} — Issue #{number} imported
   ```
 
 ### 5. 分配 Issue Assignee
 
-如果 task.md 中存在有效的 `issue_number`，将 Issue 分配给当前执行者：
-
-```bash
-gh issue edit {issue-number} --add-assignee @me 2>/dev/null || true
-```
-
-参见 `.agents/rules/issue-sync.md` 的 Assignee 同步规则。
+如果 task.md 中存在有效的 `issue_number`，按 `.agents/rules/issue-pr-commands.md` 的 Issue 更新命令为当前执行者添加 assignee；Assignee 同步的边界仍遵循 `.agents/rules/issue-sync.md`。
 
 ### 6. 完成校验
 

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

@@ -12,9 +12,8 @@ Initialize the repository's standard GitHub Labels taxonomy.
 ### 1. Verify prerequisites
 
 Confirm that:
-- `gh` is installed
-- `gh auth token` succeeds
-- `gh repo view --json nameWithOwner` can access the current repository
+- read `.agents/rules/label-milestone-setup.md` first
+- use its authentication commands to verify platform access
 
 If any prerequisite fails, stop and report the matching error.
 
@@ -26,10 +25,10 @@ Execute the complete label initialization flow with:
 bash .agents/skills/init-labels/scripts/init-labels.sh
 ```
 
-The script is responsible for:
+The script and `.agents/rules/label-milestone-setup.md` are responsible for:
 - Capturing the current label snapshot before making changes
-- Creating or updating the standard label set with `gh label create --force`
-- Reporting unmatched GitHub default labels such as `question` and `wontfix`
+- Creating or updating the standard label set with the platform-specific label command
+- Reporting unmatched platform-default labels such as `question` and `wontfix`
 - Printing the final execution summary
 
 ### 3. Standard taxonomy
@@ -68,10 +67,7 @@ Show the current mapping and ask whether it should be updated.
 #### 4.3 Write the mapping and create labels
 
 1. Write the final mapping to `.agents/.airc.json` under `labels.in`.
-2. Create one `in: {key}` label for each mapping key:
-   ```bash
-   gh label create "in: {key}" --color EBF8DF --description "Module: {key}" --force
-   ```
+2. Create one `in: {key}` label for each mapping key by following the label-create command in `.agents/rules/label-milestone-setup.md`.
 3. After user confirmation, delete stale `in:` labels that are no longer present in the final mapping.
 
 ### 5. Output and behavior guarantees
@@ -80,11 +76,11 @@ The summary must include:
 - Number of common labels created or updated
 - The written `labels.in` mapping
 - The number of `in:` labels derived from the mapping keys
-- Confirmation that exact-match GitHub defaults were overwritten
-- Any unmatched GitHub default labels still present
+- Confirmation that exact-match platform defaults were overwritten
+- Any unmatched platform-default labels still present
 
 Operational notes:
-- The operation is idempotent because every label uses `gh label create --force`.
+- The operation is idempotent because the rule-file command updates or overwrites existing labels in place.
 - `in:` labels are managed by the AI-guided step together with the `.airc.json` mapping.
 
 ### 6. Inform User

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

@@ -12,9 +12,8 @@ description: "初始化仓库的 GitHub Labels 体系"
 ### 1. 验证前置条件
 
 确认以下条件成立：
-- 已安装 `gh`
-- `gh auth token` 执行成功
-- `gh repo view --json nameWithOwner` 可以访问当前仓库
+- 执行前先读取 `.agents/rules/label-milestone-setup.md`
+- 按其中的认证命令验证平台访问能力
 
 如果任一条件失败，停止并输出对应错误。
 
@@ -26,10 +25,10 @@ description: "初始化仓库的 GitHub Labels 体系"
 bash .agents/skills/init-labels/scripts/init-labels.sh
 ```
 
-脚本负责：
+脚本与 `.agents/rules/label-milestone-setup.md` 共同负责：
 - 在修改前保存当前 label 快照
-- 使用 `gh label create --force` 创建或更新标准 label 集合
-- 提示仍然存在的 GitHub 默认 labels，例如 `question` 和 `wontfix`
+- 使用平台对应的 label 创建或更新命令维护标准 label 集合
+- 提示仍然存在的平台预置 labels，例如 `question` 和 `wontfix`
 - 输出最终执行摘要
 
 ### 3. 标准分类体系
@@ -68,10 +67,7 @@ bash .agents/skills/init-labels/scripts/init-labels.sh
 #### 4.3 写入配置并创建 label
 
 1. 将最终映射写入 `.agents/.airc.json` 的 `labels.in` 字段。
-2. 为每个映射 key 创建 `in: {key}` label：
-   ```bash
-   gh label create "in: {key}" --color EBF8DF --description "Module: {key}" --force
-   ```
+2. 为每个映射 key 按 `.agents/rules/label-milestone-setup.md` 的 label 创建命令创建 `in: {key}` label。
 3. 询问用户确认后，清理不在最终映射中的旧 `in:` label。
 
 ### 5. 输出与行为保证
@@ -80,11 +76,11 @@ bash .agents/skills/init-labels/scripts/init-labels.sh
 - 创建或更新的通用 labels 数量
 - 写入的 `labels.in` 映射结果
 - 按映射 key 计算的 `in:` labels 数量
-- 名称完全匹配的 GitHub 默认 labels 已被覆盖的说明
-- 仍然存在的未匹配 GitHub 默认 labels
+- 名称完全匹配的平台预置 labels 已被覆盖的说明
+- 仍然存在的未匹配平台预置 labels
 
 执行说明：
-- 整个操作具备幂等性，因为每个 label 都使用 `gh label create --force`。
+- 整个操作具备幂等性，因为规则文件中的 label 创建命令按覆盖或更新方式执行。
 - `in:` labels 由 AI 引导步骤和 `.airc.json` 映射统一管理。
 
 ### 6. 告知用户

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

@@ -12,9 +12,8 @@ Initialize the repository's standard GitHub Milestones taxonomy.
 ### 1. Verify prerequisites
 
 Confirm that:
-- `gh` is installed
-- `gh auth token` succeeds
-- `gh repo view --json nameWithOwner` can access the current repository
+- read `.agents/rules/label-milestone-setup.md` first
+- use its authentication commands to verify platform access
 
 If any prerequisite fails, stop and report the matching error.
 
@@ -26,11 +25,11 @@ Execute the complete milestone initialization flow with:
 bash .agents/skills/init-milestones/scripts/init-milestones.sh "$ARGUMENTS"
 ```
 
-The script is responsible for:
+The script and `.agents/rules/label-milestone-setup.md` are responsible for:
 - Creating and cleaning up a temporary workspace
 - Detecting whether `--history` was requested
 - Resolving the version baseline from the latest `v*` Git tag, then `package.json`, then defaulting to `0.1.0`
-- Listing current milestones with `gh api "repos/$repo/milestones"`
+- Listing current milestones with the platform-specific milestone query command
 - Building the desired milestone set and creating only the missing titles
 - Printing the final execution summary
 
@@ -59,7 +58,7 @@ Operational notes:
 - General Backlog is the fallback milestone for unsorted work.
 - Without `--history`, version milestones are created only for the next patch release.
 - Historical `X.Y.Z` tags create `X.Y.x` milestones as open and `X.Y.Z` milestones as closed.
-- Repositories with many tags may hit the GitHub API rate limit.
+- Repositories with many tags may hit the platform API rate limit.
 
 ### 5. Inform User
 

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

@@ -12,9 +12,8 @@ description: "初始化仓库的 GitHub Milestones 体系"
 ### 1. 验证前置条件
 
 确认以下条件成立：
-- 已安装 `gh`
-- `gh auth token` 执行成功
-- `gh repo view --json nameWithOwner` 可以访问当前仓库
+- 执行前先读取 `.agents/rules/label-milestone-setup.md`
+- 按其中的认证命令验证平台访问能力
 
 如果任一条件失败，停止并输出对应错误。
 
@@ -26,11 +25,11 @@ description: "初始化仓库的 GitHub Milestones 体系"
 bash .agents/skills/init-milestones/scripts/init-milestones.sh "$ARGUMENTS"
 ```
 
-脚本负责：
+脚本与 `.agents/rules/label-milestone-setup.md` 共同负责：
 - 创建并清理临时工作目录
 - 检测是否传入 `--history`
 - 按“最新 `v*` Git tag → `package.json` → 默认 `0.1.0`”解析版本基线
-- 使用 `gh api "repos/$repo/milestones"` 读取当前里程碑
+- 使用平台对应的 milestones 查询命令读取当前里程碑
 - 构建目标里程碑集合，并且只创建缺失标题
 - 输出最终执行摘要
 
@@ -59,7 +58,7 @@ bash .agents/skills/init-milestones/scripts/init-milestones.sh "$ARGUMENTS"
 - General Backlog 是未分类工作的兜底里程碑。
 - 不带 `--history` 时，只为下一次 patch 发布创建版本里程碑。
 - 历史 `X.Y.Z` tag 会生成开启状态的 `X.Y.x` 和关闭状态的 `X.Y.Z`。
-- 标签较多的仓库可能触发 GitHub API rate limit。
+- 标签较多的仓库可能触发平台 API rate limit。
 
 ### 5. 告知用户
 

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

@@ -81,7 +81,7 @@ Create `.agents/workspace/active/{task-id}/{plan-artifact}`.
 Get the current time:
 
 ```bash
-date "+%Y-%m-%d %H:%M:%S"
+date "+%Y-%m-%d %H:%M:%S%:z"
 ```
 
 Update `.agents/workspace/active/{task-id}/task.md`:
@@ -93,7 +93,7 @@ Update `.agents/workspace/active/{task-id}/task.md`:
 - Mark technical-design as complete in workflow progress and include the actual round when the task template supports it
 - **Append** to `## Activity Log` (do NOT overwrite previous entries):
   ```
-  - {yyyy-MM-dd HH:mm:ss} — **Technical Design (Round {N})** by {agent} — Plan completed, awaiting human review → {artifact-filename}
+  - {YYYY-MM-DD HH:mm:ss±HH:MM} — **Technical Design (Round {N})** by {agent} — Plan completed, awaiting human review → {artifact-filename}
   ```
 
 If task.md contains a valid `issue_number`, perform these sync actions (skip and continue on any failure):

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

@@ -81,7 +81,7 @@ description: "为任务设计技术方案和实施计划"
 获取当前时间：
 
 ```bash
-date "+%Y-%m-%d %H:%M:%S"
+date "+%Y-%m-%d %H:%M:%S%:z"
 ```
 
 更新 `.agents/workspace/active/{task-id}/task.md`：
@@ -93,7 +93,7 @@ date "+%Y-%m-%d %H:%M:%S"
 - 在工作流进度中标记 technical-design 为已完成，并注明实际轮次（如果任务模板支持）
 - **追加**到 `## Activity Log`（不要覆盖之前的记录）：
   ```
-  - {yyyy-MM-dd HH:mm:ss} — **Technical Design (Round {N})** by {agent} — Plan completed, awaiting human review → {artifact-filename}
+  - {YYYY-MM-DD HH:mm:ss±HH:MM} — **Technical Design (Round {N})** by {agent} — Plan completed, awaiting human review → {artifact-filename}
   ```
 
 如果 task.md 中存在有效的 `issue_number`，执行以下同步操作（任一失败则跳过并继续）：

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

@@ -51,13 +51,13 @@ Create `.agents/workspace/active/{task-id}/{refinement-artifact}`.
 Get the current time:
 
 ```bash
-date "+%Y-%m-%d %H:%M:%S"
+date "+%Y-%m-%d %H:%M:%S%:z"
 ```
 
 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}`
+  `- {YYYY-MM-DD HH:mm:ss±HH:MM} — **Refinement (Round {N}, for {review-artifact})** by {agent} — Fixed {n} blockers, {n} major, {n} minor issues → {refinement-artifact}`
 
 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

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

@@ -51,13 +51,13 @@ description: "处理代码审查反馈并修复问题"
 获取当前时间：
 
 ```bash
-date "+%Y-%m-%d %H:%M:%S"
+date "+%Y-%m-%d %H:%M:%S%:z"
 ```
 
 更新 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}`
+  `- {YYYY-MM-DD HH:mm:ss±HH:MM} — **Refinement (Round {N}, for {review-artifact})** by {agent} — Fixed {n} blockers, {n} major, {n} minor issues → {refinement-artifact}`
 
 如果 task.md 中存在有效的 `issue_number`，执行以下同步操作（任一失败则跳过并继续）：
 - 执行前先读取 `.agents/rules/issue-sync.md`

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

@@ -11,15 +11,11 @@ Reformat the title of the specified Issue or PR to Conventional Commits format b
 
 ### 1. Identify Target and Fetch Information
 
-Try to determine if the ID is an Issue or PR:
-
-```bash
-# Try Issue first
-gh issue view <id> --json number,title,body,labels,state
+Read `.agents/rules/issue-pr-commands.md` before this step.
 
-# If not found or is a PR
-gh pr view <id> --json number,title,body,labels,state,files
-```
+Try to determine if the ID is an Issue or PR:
+- first fetch Issue data by following the "Read an Issue" command in the rule file
+- if the target is not an Issue or is actually a PR, fetch PR data by following the "Read a PR" command
 
 ### 2. Analyze Content
 
@@ -58,15 +54,9 @@ Ask user: "Apply this title? (y/n)"
 
 ### 4. Apply Change
 
-If user confirms:
-
-```bash
-# For Issue
-gh issue edit <id> --title "<new-title>"
-
-# For PR
-gh pr edit <id> --title "<new-title>"
-```
+If the user confirms:
+- for an Issue, update the title by following the "Update Issues" command in `.agents/rules/issue-pr-commands.md`
+- for a PR, update the title by following the "Update PRs" command in `.agents/rules/issue-pr-commands.md`
 
 ### 5. Inform User
 

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

@@ -11,15 +11,11 @@ description: "重构 Issue/PR 标题为 Conventional Commits 格式"
 
 ### 1. 识别目标并获取信息
 
-尝试判断 ID 是 Issue 还是 PR：
-
-```bash
-# 先尝试 Issue
-gh issue view <id> --json number,title,body,labels,state
+执行前先读取 `.agents/rules/issue-pr-commands.md`。
 
-# 如果未找到或是 PR
-gh pr view <id> --json number,title,body,labels,state,files
-```
+尝试判断 ID 是 Issue 还是 PR：
+- 先按规则文件中的“读取 Issue”命令获取 Issue 信息
+- 如果未找到或目标实际为 PR，再按规则文件中的“读取 PR”命令获取 PR 信息
 
 ### 2. 分析内容
 
@@ -59,14 +55,8 @@ Issue/PR #{id} 分析结果：
 ### 4. 应用修改
 
 如果用户确认：
-
-```bash
-# 对于 Issue
-gh issue edit <id> --title "<new-title>"
-
-# 对于 PR
-gh pr edit <id> --title "<new-title>"
-```
+- 对于 Issue：按 `.agents/rules/issue-pr-commands.md` 中的 “Issue 更新” 命令设置标题
+- 对于 PR：按 `.agents/rules/issue-pr-commands.md` 中的 “PR 更新” 命令设置标题
 
 ### 5. 告知用户
 

package/templates/.agents/skills/release/{SKILL.md → SKILL.en.md}

@@ -113,7 +113,8 @@ bash .agents/skills/release/scripts/manage-milestones.sh "$MAJOR" "$MINOR" "$PAT
 ```
 
 The script is responsible for:
-- Loading the current milestone list with `gh api "repos/$repo/milestones"`
+- Read `.agents/rules/label-milestone-setup.md` before this step
+- Use its milestone list and update commands to load and adjust current milestones
 - Closing `{MAJOR}.{MINOR}.{PATCH}` when it exists and is still open
 - Ensuring `{MAJOR}.{MINOR}.{PATCH+1}` and `{MAJOR}.{MINOR}.x` exist
 - When `PATCH=0`, also ensuring `{MAJOR}.{MINOR+1}.0` and `{MAJOR}.{MINOR+1}.x`

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

@@ -113,7 +113,8 @@ bash .agents/skills/release/scripts/manage-milestones.sh "$MAJOR" "$MINOR" "$PAT
 ```
 
 脚本负责：
-- 使用 `gh api "repos/$repo/milestones"` 读取当前里程碑
+- 执行前先读取 `.agents/rules/label-milestone-setup.md`
+- 使用其中的 milestone 查询与更新命令读取和调整当前里程碑
 - 在 `{MAJOR}.{MINOR}.{PATCH}` 存在且仍为开启状态时将其关闭
 - 确保 `{MAJOR}.{MINOR}.{PATCH+1}` 与 `{MAJOR}.{MINOR}.x` 存在
 - 当 `PATCH=0` 时，同时确保 `{MAJOR}.{MINOR+1}.0` 与 `{MAJOR}.{MINOR+1}.x`

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

@@ -1,11 +1,11 @@
 ---
 name: restore-task
-description: "Restore local task files from GitHub Issue comments"
+description: "Restore local task files from platform Issue comments"
 ---
 
 # Restore Task
 
-Restore local task workspace files from GitHub Issue comments that contain sync markers.
+Restore local task workspace files from platform Issue comments that contain sync markers.
 
 ## Boundary / Critical Rules
 
@@ -21,19 +21,13 @@ Restore local task workspace files from GitHub Issue comments that contain sync
 Check:
 - required `{issue-number}`
 - optional `{task-id}`
-- `gh auth status`
+- read `.agents/rules/issue-pr-commands.md` first and use its authentication commands to verify current platform access
 
 If the user provided `{task-id}`, validate the `TASK-{yyyyMMdd-HHmmss}` format.
 
 ### 2. Fetch Issue Comments
 
-Read all Issue comments while preserving the original order and comment IDs.
-
-Suggested command:
-
-```bash
-gh api "repos/{owner}/{repo}/issues/{issue-number}/comments" --paginate
-```
+Read all Issue comments by following the "Read Issue comments" command in `.agents/rules/issue-pr-commands.md`, preserving the original order and comment IDs.
 
 ### 3. Determine the task-id and Files to Restore
 
@@ -87,7 +81,7 @@ Write only files that were actually recovered from Issue comments. Do not invent
 Get the current time:
 
 ```bash
-date "+%Y-%m-%d %H:%M:%S"
+date "+%Y-%m-%d %H:%M:%S%:z"
 ```
 
 Update the restored `task.md`:
@@ -97,7 +91,7 @@ Update the restored `task.md`:
 - keep the original `current_step`
 - append this entry to `## Activity Log`:
   ```
-  - {yyyy-MM-dd HH:mm:ss} — **Restore Task** by {agent} — Restored task from Issue #{issue-number}
+  - {YYYY-MM-DD HH:mm:ss±HH:MM} — **Restore Task** by {agent} — Restored task from Issue #{issue-number}
   ```
 
 ### 7. Verification Gate
@@ -152,7 +146,7 @@ Stop after completing the checklist. Do not continue the workflow automatically.
 ## Error Handling
 
 - Issue missing or inaccessible
-- `gh` unavailable or unauthenticated
+- Platform CLI unavailable or unauthenticated
 - No sync-marked comments found
 - Unable to determine a unique `task-id`
 - Target directory already exists

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

@@ -1,11 +1,11 @@
 ---
 name: restore-task
-description: "从 GitHub Issue 评论还原本地任务文件"
+description: "从平台 Issue 评论还原本地任务文件"
 ---
 
 # 还原任务
 
-从带有 sync 标记的 GitHub Issue 评论中恢复本地任务工作区文件。
+从带有 sync 标记的平台 Issue 评论中恢复本地任务工作区文件。
 
 ## 行为边界 / 关键规则
 
@@ -21,19 +21,13 @@ description: "从 GitHub Issue 评论还原本地任务文件"
 检查：
 - 必填参数 `{issue-number}`
 - 可选参数 `{task-id}`
-- `gh auth status`
+- 执行前先读取 `.agents/rules/issue-pr-commands.md`，并按其中的认证命令验证当前平台访问能力
 
 如果用户传入了 `{task-id}`，校验其格式为 `TASK-{yyyyMMdd-HHmmss}`。
 
 ### 2. 获取 Issue 评论
 
-读取 Issue 的全部评论，保留原始顺序和评论 ID。
-
-建议命令：
-
-```bash
-gh api "repos/{owner}/{repo}/issues/{issue-number}/comments" --paginate
-```
+按 `.agents/rules/issue-pr-commands.md` 中的 “Issue 评论读取” 命令读取 Issue 的全部评论，保留原始顺序和评论 ID。
 
 ### 3. 确定 task-id 与待恢复文件
 
@@ -87,7 +81,7 @@ gh api "repos/{owner}/{repo}/issues/{issue-number}/comments" --paginate
 获取当前时间：
 
 ```bash
-date "+%Y-%m-%d %H:%M:%S"
+date "+%Y-%m-%d %H:%M:%S%:z"
 ```
 
 更新恢复出的 `task.md`：
@@ -97,7 +91,7 @@ date "+%Y-%m-%d %H:%M:%S"
 - 保留原 `current_step`
 - 在 `## 活动日志` 追加：
   ```
-  - {yyyy-MM-dd HH:mm:ss} — **Restore Task** by {agent} — Restored task from Issue #{issue-number}
+  - {YYYY-MM-DD HH:mm:ss±HH:MM} — **Restore Task** by {agent} — Restored task from Issue #{issue-number}
   ```
 
 ### 7. 完成校验
@@ -152,7 +146,7 @@ node .agents/scripts/validate-artifact.js gate restore-task .agents/workspace/ac
 ## 错误处理
 
 - Issue 不存在或无权访问
-- `gh` 未认证
+- 平台 CLI 未认证
 - 找不到带 sync 标记的评论
 - 无法唯一确定 `task-id`
 - 目标目录已存在

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

@@ -47,11 +47,11 @@ Create `.agents/workspace/active/{task-id}/{review-artifact}`.
 Get the current time:
 
 ```bash
-date "+%Y-%m-%d %H:%M:%S"
+date "+%Y-%m-%d %H:%M:%S%:z"
 ```
 
 Update task.md and append:
-`- {yyyy-MM-dd HH:mm:ss} — **Code Review (Round {N})** by {agent} — Verdict: {Approved/Changes Requested/Rejected}, blockers: {n}, major: {n}, minor: {n} → {artifact-filename}`
+`- {YYYY-MM-DD HH:mm:ss±HH:MM} — **Code Review (Round {N})** by {agent} — Verdict: {Approved/Changes Requested/Rejected}, blockers: {n}, major: {n}, minor: {n} → {artifact-filename}`
 
 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

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

@@ -47,11 +47,11 @@ description: "审查任务实现并输出代码审查报告"
 获取当前时间：
 
 ```bash
-date "+%Y-%m-%d %H:%M:%S"
+date "+%Y-%m-%d %H:%M:%S%:z"
 ```
 
 更新 task.md，并追加：
-`- {yyyy-MM-dd HH:mm:ss} — **Code Review (Round {N})** by {agent} — Verdict: {Approved/Changes Requested/Rejected}, blockers: {n}, major: {n}, minor: {n} → {artifact-filename}`
+`- {YYYY-MM-DD HH:mm:ss±HH:MM} — **Code Review (Round {N})** by {agent} — Verdict: {Approved/Changes Requested/Rejected}, blockers: {n}, major: {n}, minor: {n} → {artifact-filename}`
 
 如果 task.md 中存在有效的 `issue_number`，执行以下同步操作（任一失败则跳过并继续）：
 - 执行前先读取 `.agents/rules/issue-sync.md`