@fitlab-ai/agent-infra 0.5.1 → 0.5.3

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

@@ -8,7 +8,7 @@ description: "标记任务完成并归档"
 ## 行为边界 / 关键规则
 
 - 本命令更新任务元数据并物理移动任务目录
-- 除非强制执行，不要归档有未完成工作流步骤的任务
+- 除非强制执行，不要转移有未完成工作流步骤的任务
 
 ## 执行步骤
 
@@ -36,7 +36,7 @@ description: "标记任务完成并归档"
 > - 如果任意一个条件不满足 → **默认停止**，输出前置条件未满足的警告
 > - 只有用户明确要求 `--force` 时，才可以在前置条件未满足时继续
 >
-> **禁止在前置条件未满足时继续执行步骤 3-7，也不要输出「任务 {task-id} 已完成并归档。」**
+> **禁止在前置条件未满足时继续执行步骤 3-7，也不要输出「任务 {task-id} 已完成，任务目录已转移到 completed/。」**
 
 如果任何前置条件未满足，警告用户：
 ```
@@ -53,7 +53,7 @@ Please complete the missing steps first, or use --force to override.
 获取当前时间：
 
 ```bash
-date "+%Y-%m-%d %H:%M:%S"
+date "+%Y-%m-%d %H:%M:%S%:z"
 ```
 
 更新 `.agents/workspace/active/{task-id}/task.md`：
@@ -64,10 +64,10 @@ date "+%Y-%m-%d %H:%M:%S"
 - 逐项验证并勾选 `## 完成检查清单` 中的所有条目（将 `- [ ]` 改为 `- [x]`）
 - **追加**到 `## Activity Log`（不要覆盖之前的记录）：
   ```
-  - {yyyy-MM-dd HH:mm:ss} — **Completed** by {agent} — Task archived to completed/
+  - {YYYY-MM-DD HH:mm:ss±HH:MM} — **Completed** by {agent} — Task moved to completed/
   ```
 
-### 4. 归档任务
+### 4. 转移任务
 
 将任务目录从 active 移动到 completed：
 
@@ -75,7 +75,7 @@ date "+%Y-%m-%d %H:%M:%S"
 mv .agents/workspace/active/{task-id} .agents/workspace/completed/{task-id}
 ```
 
-### 5. 验证归档
+### 5. 验证转移
 
 ```bash
 ls .agents/workspace/completed/{task-id}/task.md
@@ -116,12 +116,12 @@ node .agents/scripts/validate-artifact.js gate complete-task .agents/workspace/c
 
 输出格式：
 ```
-任务 {task-id} 已完成并归档。
+任务 {task-id} 已完成，任务目录已转移到 completed/。
 
 任务信息：
 - 标题：{title}
 - 完成时间：{timestamp}
-- 归档路径：.agents/workspace/completed/{task-id}/
+- 目标路径：.agents/workspace/completed/{task-id}/
 
 交付物：
 - {关键产出列表：修改的文件、添加的测试等}
@@ -132,18 +132,18 @@ node .agents/scripts/validate-artifact.js gate complete-task .agents/workspace/c
 - [ ] 验证了所有工作流步骤已完成
 - [ ] 更新了 task.md 的完成状态和时间戳
 - [ ] 将任务目录移动到 `.agents/workspace/completed/`
-- [ ] 验证了归档成功
+- [ ] 验证了转移成功
 - [ ] 告知了用户完成情况
 
 ## 注意事项
 
-1. **过早完成**：不要归档有未完成步骤的任务。未完成的情况示例：
+1. **过早完成**：不要转移有未完成步骤的任务。未完成的情况示例：
    - 代码已编写但未提交
    - 代码已提交但未审查
    - 审查发现阻塞项但未修复
    - PR 已创建但未合并
 
-2. **回滚**：如果任务被错误归档：
+2. **回滚**：如果任务被错误转移：
    ```bash
    mv .agents/workspace/completed/{task-id} .agents/workspace/active/{task-id}
    ```

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

@@ -21,7 +21,7 @@ Create the base GitHub Issue from `task.md` and write `issue_number` back to the
 
 Check:
 - `.agents/workspace/active/{task-id}/task.md`
-- GitHub CLI authentication with `gh auth status`
+- read `.agents/rules/issue-pr-commands.md` first, then use its authentication commands to verify platform access
 
 If `issue_number` already exists and is not empty or `N/A`, confirm with the user before creating a replacement Issue.
 
@@ -39,17 +39,14 @@ Detect `.github/ISSUE_TEMPLATE` files and decide whether to use a matched templa
 
 ### 4. Create the Issue
 
-Create the Issue with `gh issue create --title "{title}" --body "{body}" --assignee @me ...` and omit `--label` when nothing valid remains.
-
-If an Issue Type was selected, set it with:
-`gh api "repos/$repo/issues/{issue-number}" -X PATCH -f type="{issue-type}" --silent`
+Create and enrich the Issue by following the "Create Issue" and "Set the Issue Type" sections in `.agents/rules/issue-pr-commands.md`. Omit label arguments when nothing valid remains.
 
 ### 5. Update Task Status
 
 Get the current time:
 
 ```bash
-date "+%Y-%m-%d %H:%M:%S"
+date "+%Y-%m-%d %H:%M:%S%:z"
 ```
 
 Write back `issue_number`, update `updated_at`, and append the Create Issue Activity Log entry.

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

@@ -21,7 +21,7 @@ description: "从任务文件创建 GitHub Issue"
 
 检查：
 - `.agents/workspace/active/{task-id}/task.md`
-- 使用 `gh auth status` 验证 GitHub CLI 认证状态
+- 执行前先读取 `.agents/rules/issue-pr-commands.md`，并按其中的认证命令验证当前平台访问能力
 
 如果 `issue_number` 已存在且既不为空也不为 `N/A`，创建前必须先与用户确认。
 
@@ -39,17 +39,14 @@ description: "从任务文件创建 GitHub Issue"
 
 ### 4. 创建 Issue
 
-使用 `gh issue create --title "{title}" --body "{body}" --assignee @me ...` 创建 Issue；如果没有有效 label，就省略 `--label`。
-
-如果已经确定了 Issue Type，则执行：
-`gh api "repos/$repo/issues/{issue-number}" -X PATCH -f type="{issue-type}" --silent`
+按 `.agents/rules/issue-pr-commands.md` 中的 “创建 Issue” 与 “Issue Type 设置” 规则创建并补充 Issue；如果没有有效 label，就省略 label 参数。
 
 ### 5. 更新任务状态
 
 获取当前时间：
 
 ```bash
-date "+%Y-%m-%d %H:%M:%S"
+date "+%Y-%m-%d %H:%M:%S%:z"
 ```
 
 回写 `issue_number`，更新 `updated_at`，并追加 Create Issue 的 Activity Log。

package/templates/.agents/skills/create-issue/reference/{label-and-type.md → label-and-type.en.md}

@@ -42,29 +42,17 @@ Issue Type fallback mapping:
 
 ## Create the Issue
 
-Use:
+Before creating the Issue, read `.agents/rules/issue-pr-commands.md` and use its "Create an Issue" command template.
 
-```bash
-gh issue create --title "{title}" --body "{body}" --label "{label-1}" --label "{label-2}" --milestone "{milestone}"
-```
-
-If no valid labels remain, omit `--label`.
+If no valid labels remain, omit label arguments.
 
 For milestone inference, read `.agents/rules/milestone-inference.md` and follow "Phase 1: `create-issue`" before creating the Issue.
 
-Issue Type setup:
-
-```bash
-gh api "orgs/$owner/issue-types" --jq '.[].name'
-gh api "repos/$repo/issues/{issue-number}" -X PATCH -f type="{issue-type}" --silent
-```
+Issue Type setup follows the matching commands in `.agents/rules/issue-pr-commands.md`.
 
 `in:` labels (coarse selection):
 
-```bash
-gh label list --search "in:" --limit 50 --json name --jq '.[].name'
-gh issue edit {issue-number} --add-label "in: {module}"
-```
+Prepare label edit arguments by following the Issue update command in `.agents/rules/issue-pr-commands.md`.
 
 Use the returned labels to do semantic matching against the task.md title and description:
 - add a label when the task **explicitly mentions** a module (for example, "fix CLI argument parsing" -> `in: cli`)

package/templates/.agents/skills/create-issue/reference/label-and-type.zh-CN.md

@@ -42,29 +42,17 @@ Issue Type fallback 映射：
 
 ## 创建 Issue
 
-使用：
+创建 Issue 时，执行前先读取 `.agents/rules/issue-pr-commands.md`，并使用其中的 “创建 Issue” 命令模板。
 
-```bash
-gh issue create --title "{title}" --body "{body}" --label "{label-1}" --label "{label-2}" --milestone "{milestone}"
-```
-
-如果最终没有有效 label，就省略 `--label`。
+如果最终没有有效 label，就省略 label 参数。
 
 Milestone 推断规则见 `.agents/rules/milestone-inference.md` 的「阶段 1：`create-issue`」。推断前先读取该文件。
 
-Issue Type 设置：
-
-```bash
-gh api "orgs/$owner/issue-types" --jq '.[].name'
-gh api "repos/$repo/issues/{issue-number}" -X PATCH -f type="{issue-type}" --silent
-```
+Issue Type 设置同样遵循 `.agents/rules/issue-pr-commands.md` 中的对应命令。
 
 `in:` label（粗选）：
 
-```bash
-gh label list --search "in:" --limit 50 --json name --jq '.[].name'
-gh issue edit {issue-number} --add-label "in: {module}"
-```
+执行前先按 `.agents/rules/issue-pr-commands.md` 的 Issue 更新命令准备 label 编辑参数。
 
 从查询结果中，根据 task.md 的标题和描述进行语义匹配：
 - 任务描述**明确提及**某个模块（如"修复 CLI 参数解析"→ `in: cli`）→ 添加

package/templates/.agents/skills/create-pr/{SKILL.md → SKILL.en.md}

@@ -38,16 +38,15 @@ Confirm whether the current branch already has an upstream. Push with `git push
 
 Check whether the current branch already has a PR first; if one exists, show the PR URL and stop without repeating metadata sync or summary publication.
 
-Create the PR with `gh pr create --base <target-branch> --title "<title>" --assignee @me --body ...`.
+Read `.agents/rules/issue-pr-commands.md` before this step, then create the PR with its "Create a PR" command template.
 
 If `{task-id}` is available and the related task provides `issue_number`, keep `Closes #{issue-number}` in the PR body.
 
 ### 6. Sync PR Metadata
 
 For PRs where `{task-id}` is available, sync the core metadata immediately:
-- run `gh label list --search "type:" --limit 1 --json name --jq 'length'`
-- add the mapped type label with `gh pr edit {pr-number} --add-label "{type-label}"`
-- add relevant `in: {module}` labels with `gh pr edit {pr-number} --add-label "in: {module}"`
+- query standard labels, Issue metadata, and PR metadata via `.agents/rules/issue-pr-commands.md`
+- add the mapped type label and relevant `in:` labels with the PR update command from `.agents/rules/issue-pr-commands.md`
 - sync the linked Issue `in:` labels to match by following the `in:` label sync rule in `.agents/rules/issue-sync.md`
 - reuse the Issue milestone by following "Phase 3: `create-pr`" in `.agents/rules/milestone-inference.md`
 - keep Development linking in the PR body with `Closes #{issue-number}` when applicable
@@ -70,7 +69,7 @@ Aggregate a reviewer-facing summary from those artifacts and maintain a single i
 Get the current time:
 
 ```bash
-date "+%Y-%m-%d %H:%M:%S"
+date "+%Y-%m-%d %H:%M:%S%:z"
 ```
 
 If `{task-id}` is available, update task.md with `pr_number`, `updated_at`, and append the PR Created Activity Log entry including metadata-sync and summary results.

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

@@ -38,16 +38,15 @@ description: "创建 Pull Request 到目标分支"
 
 先检查当前分支是否已经存在 PR；如果已存在，直接告知用户 PR URL 并结束，不要重复执行元数据同步或摘要发布。
 
-使用 `gh pr create --base <target-branch> --title "<title>" --assignee @me --body ...` 创建 PR。
+执行前先读取 `.agents/rules/issue-pr-commands.md`，并按其中的 “创建 PR” 命令创建 PR。
 
 如果获取到 `{task-id}` 且对应任务提供了 `issue_number`，必须在 PR 正文中保留 `Closes #{issue-number}`。
 
 ### 6. 同步 PR 元数据
 
 对获取到 `{task-id}` 的 PR，立即同步这些核心元数据：
-- 执行 `gh label list --search "type:" --limit 1 --json name --jq 'length'`
-- 使用 `gh pr edit {pr-number} --add-label "{type-label}"` 添加 type label
-- 使用 `gh pr edit {pr-number} --add-label "in: {module}"` 添加相关 `in:` labels
+- 按 `.agents/rules/issue-pr-commands.md` 查询标准 label / Issue / PR 元数据
+- 按 `.agents/rules/issue-pr-commands.md` 的 PR 更新命令添加 type label 与相关 `in:` labels
 - 按 `.agents/rules/issue-sync.md` 的 `in:` label 同步规则，同步更新关联 Issue 的 `in:` label 保持一致
 - 按 `.agents/rules/milestone-inference.md` 的「阶段 3：`create-pr`」复用 Issue milestone
 - 通过 `Closes #{issue-number}` 保持 Development 关联
@@ -70,7 +69,7 @@ description: "创建 Pull Request 到目标分支"
 获取当前时间：
 
 ```bash
-date "+%Y-%m-%d %H:%M:%S"
+date "+%Y-%m-%d %H:%M:%S%:z"
 ```
 
 如果获取到了 `{task-id}`，更新 task.md 的 `pr_number`、`updated_at`，并追加 PR Created 的 Activity Log，记录元数据同步和摘要发布结果。

package/templates/.agents/skills/create-pr/reference/{pr-body-template.md → pr-body-template.en.md}

@@ -25,6 +25,8 @@ git diff <target-branch>...HEAD
 
 ## Sync PR Metadata
 
+Read `.agents/rules/issue-pr-commands.md` before this step.
+
 Before syncing labels, verify the standard label system:
 
 ```bash
@@ -47,9 +49,9 @@ Type label mapping:
 | other values | skip |
 
 Metadata sync order:
-1. query Issue labels and milestone best-effort with `gh issue view {issue-number} --json labels,milestone`
-2. add the mapped type label with `gh pr edit {pr-number} --add-label "{type-label}"`
-3. inherit non-`type:` and non-`status:` Issue labels with repeated `gh pr edit ... --add-label`
+1. query Issue labels and milestone via the Issue read command in `.agents/rules/issue-pr-commands.md`
+2. add the mapped type label via the PR update command in `.agents/rules/issue-pr-commands.md`
+3. inherit non-`type:` and non-`status:` Issue labels via repeated PR update commands from the same rule
 4. refine the PR `in:` labels by following `.agents/rules/issue-sync.md`, and keep the linked Issue `in:` labels in sync with the same result
 5. handle the milestone by following "Phase 3: `create-pr`" in `.agents/rules/milestone-inference.md`, reusing the Issue milestone directly
 6. ensure the PR body contains `Closes #{issue-number}` or an equivalent closing keyword
@@ -61,20 +63,13 @@ Milestone rule:
 ## Create the PR
 
 - Extract `issue_number` from task.md when this work belongs to an active task
-- If `issue_number` exists, query the Issue best-effort with `gh issue view {issue-number} --json number,title --jq '.number'`
-- Before calling `gh pr create`, check whether the current branch already has a PR. If it does, report the PR URL and state, then stop without repeating metadata sync or summary publication
+- If `issue_number` exists, query the Issue via `.agents/rules/issue-pr-commands.md`
+- Before calling the PR creation command, check whether the current branch already has a PR. If it does, report the PR URL and state, then stop without repeating metadata sync or summary publication
 - Use HEREDOC to pass the PR body
 - Replace `{$IssueNumber}` in the template when present
 - End the PR body with `Generated with AI assistance`
 
-```bash
-gh pr create --base <target-branch> --title "<title>" --assignee @me --body "$(cat <<'EOF'
-<Complete PR description following template>
-
-Generated with AI assistance
-EOF
-)"
-```
+Create the PR with the "Create a PR" command template in `.agents/rules/issue-pr-commands.md`.
 
 Final user output should include this follow-up path:
 

package/templates/.agents/skills/create-pr/reference/pr-body-template.zh-CN.md

@@ -25,6 +25,8 @@ git diff <target-branch>...HEAD
 
 ## 同步 PR 元数据
 
+执行前先读取 `.agents/rules/issue-pr-commands.md`。
+
 在同步 label 之前，先确认标准 label 体系已经存在：
 
 ```bash
@@ -47,9 +49,9 @@ Type label 映射：
 | 其他值 | 跳过 |
 
 元数据同步顺序：
-1. 用 `gh issue view {issue-number} --json labels,milestone` 尽力查询 Issue 的 labels 和 milestone
-2. 用 `gh pr edit {pr-number} --add-label "{type-label}"` 添加映射后的 type label
-3. 用重复的 `gh pr edit ... --add-label` 继承非 `type:`、非 `status:` 的 Issue labels
+1. 按 `.agents/rules/issue-pr-commands.md` 的 Issue 读取命令查询关联 Issue 的 labels 和 milestone
+2. 按 `.agents/rules/issue-pr-commands.md` 的 PR 更新命令添加映射后的 type label
+3. 按同一规则的 PR 更新命令继承非 `type:`、非 `status:` 的 Issue labels
 4. 按 `.agents/rules/issue-sync.md` 的 `in:` label 同步规则精修 PR 的 `in:` label，同时同步更新关联 Issue 的 `in:` label 保持一致
 5. 按 `.agents/rules/milestone-inference.md` 的「阶段 3：`create-pr`」处理 milestone，直接复用 Issue milestone
 6. 确保 PR 正文包含 `Closes #{issue-number}` 或等价的 closing keyword
@@ -61,20 +63,13 @@ Milestone 规则：
 ## 创建 PR
 
 - 当当前工作属于活动任务时，从 task.md 中提取 `issue_number`
-- 如果存在 `issue_number`，用 `gh issue view {issue-number} --json number,title --jq '.number'` 尽力查询对应 Issue
-- 在调用 `gh pr create` 前，先检查当前分支是否已经存在 PR；如果已存在，直接告知用户 PR URL 和状态并结束，不要重复同步元数据或摘要
+- 如果存在 `issue_number`，按 `.agents/rules/issue-pr-commands.md` 的 Issue 读取命令查询对应 Issue
+- 在调用 PR 创建命令前，先检查当前分支是否已经存在 PR；如果已存在，直接告知用户 PR URL 和状态并结束，不要重复同步元数据或摘要
 - 使用 HEREDOC 传递 PR 正文
 - 如果模板中存在 `{$IssueNumber}`，替换它
 - PR 正文结尾必须带上 `Generated with AI assistance`
 
-```bash
-gh pr create --base <target-branch> --title "<title>" --assignee @me --body "$(cat <<'EOF'
-<Complete PR description following template>
-
-Generated with AI assistance
-EOF
-)"
-```
+创建 PR 时，使用 `.agents/rules/issue-pr-commands.md` 中的 “创建 PR” 命令模板。
 
 最终用户输出必须按顺序包含以下后续动作：
 

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

@@ -35,12 +35,10 @@ git rev-parse v<prev-version>
 
 Fetch multiple published release notes as format references, then use a predefined complete category list:
 
+Read `.agents/rules/release-commands.md` before this step.
+
 ```bash
-# Part A: Fetch the body for each of the 3 releases
-for tag in $(gh release list --limit 10 --json tagName,isDraft,isPrerelease \
-  --jq '[.[] | select(.isDraft == false and .isPrerelease == false)] | .[0:3] | .[].tagName'); do
-  gh release view "$tag" --json body -q '.body'
-done
+# Part A: fetch the latest 3 published release bodies by following the release query commands in `.agents/rules/release-commands.md`
 ```
 
 **Part B: Complete Category List**
@@ -65,10 +63,7 @@ Get the date range between tags, then query merged PRs:
 git log v<prev-version> --format=%aI -1
 git log v<version> --format=%aI -1
 
-# Get merged PRs in range
-gh pr list --state merged --base <branch> \
-  --json number,title,body,author,labels,mergedAt,url \
-  --limit 200 --search "merged:YYYY-MM-DD..YYYY-MM-DD"
+# Get merged PRs in range by following the merged-PR query command in `.agents/rules/release-commands.md`
 ```
 
 Also collect direct commits without PRs:
@@ -81,9 +76,7 @@ git log v<prev-version>..v<version> --format="%H %s" --no-merges
 From each PR body, extract linked Issues:
 - Match patterns: `Closes #N`, `Fixes #N`, `Resolves #N` (case-insensitive)
 
-```bash
-gh issue view <N> --json number,title,labels,url
-```
+Read linked Issues by following `.agents/rules/release-commands.md`.
 
 ### 6. Classify Changes
 
@@ -135,12 +128,7 @@ Ask:
 
 ### 9. Create Draft Release (If Confirmed)
 
-```bash
-gh release create v<version> \
-  --title "v<version>" \
-  --notes-file /tmp/release-notes-v<version>.md \
-  --draft
-```
+Create the draft release by following `.agents/rules/release-commands.md`.
 
 Output:
 ```

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

@@ -35,12 +35,10 @@ git rev-parse v<prev-version>
 
 获取最近多条已发布的 Release Note 作为格式参考，并参考预定义的完整分类清单：
 
+执行前先读取 `.agents/rules/release-commands.md`。
+
 ```bash
-# Part A: 逐条获取这 3 条 Release 的 body
-for tag in $(gh release list --limit 10 --json tagName,isDraft,isPrerelease \
-  --jq '[.[] | select(.isDraft == false and .isPrerelease == false)] | .[0:3] | .[].tagName'); do
-  gh release view "$tag" --json body -q '.body'
-done
+# Part A：按 `.agents/rules/release-commands.md` 的 release 查询命令逐条获取最近 3 条 Release 的 body
 ```
 
 **Part B：完整分类清单**
@@ -65,10 +63,7 @@ done
 git log v<prev-version> --format=%aI -1
 git log v<version> --format=%aI -1
 
-# 获取范围内已合并的 PR
-gh pr list --state merged --base <branch> \
-  --json number,title,body,author,labels,mergedAt,url \
-  --limit 200 --search "merged:YYYY-MM-DD..YYYY-MM-DD"
+# 获取范围内已合并的 PR（按 `.agents/rules/release-commands.md` 的 merged PR 查询命令执行）
 ```
 
 同时收集没有 PR 的直接提交：
@@ -81,9 +76,7 @@ git log v<prev-version>..v<version> --format="%H %s" --no-merges
 从每个 PR body 中提取关联的 Issue：
 - 匹配模式：`Closes #N`、`Fixes #N`、`Resolves #N`（不区分大小写）
 
-```bash
-gh issue view <N> --json number,title,labels,url
-```
+按 `.agents/rules/release-commands.md` 的关联 Issue 查询命令读取。
 
 ### 6. 分类变更
 
@@ -135,12 +128,7 @@ gh issue view <N> --json number,title,labels,url
 
 ### 9. 创建 Draft Release（如确认）
 
-```bash
-gh release create v<version> \
-  --title "v<version>" \
-  --notes-file /tmp/release-notes-v<version>.md \
-  --draft
-```
+按 `.agents/rules/release-commands.md` 的 Draft Release 创建命令执行。
 
 输出：
 ```

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

@@ -71,8 +71,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}
@@ -85,7 +85,7 @@ Note: `created_by` is `human` because the task comes from the user's description
 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`:
@@ -95,7 +95,7 @@ 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} — **Task Created** by {agent} — Task created from description
+  - {YYYY-MM-DD HH:mm:ss±HH:MM} — **Task Created** by {agent} — Task created from description
   ```
 
 ### 4. Verification Gate

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

@@ -71,8 +71,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 代理}
@@ -85,7 +85,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`：
@@ -95,7 +95,7 @@ date "+%Y-%m-%d %H:%M:%S"
 - `## 上下文` 中的 `- **分支**：`：更新为生成的分支名
 - **追加**到 `## Activity Log`（不要覆盖之前的记录）：
   ```
-  - {yyyy-MM-dd HH:mm:ss} — **Task Created** by {agent} — Task created from description
+  - {YYYY-MM-DD HH:mm:ss±HH:MM} — **Task Created** by {agent} — Task created from description
   ```
 
 ### 4. 完成校验

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

@@ -81,7 +81,7 @@ Create `.agents/workspace/active/{task-id}/{implementation-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`:
@@ -91,7 +91,7 @@ Update `.agents/workspace/active/{task-id}/task.md`:
 - review the `## Requirements` section and only change items from `- [ ]` to `- [x]` when they are clearly satisfied by this round's implemented code and passing tests
 - record `{implementation-artifact}` for Round `{implementation-round}`
 - append:
-  `- {yyyy-MM-dd HH:mm:ss} — **Implementation (Round {N})** by {agent} — Code implemented, {n} files modified, {n} tests passed → {implementation-artifact}`
+  `- {YYYY-MM-DD HH:mm:ss±HH:MM} — **Implementation (Round {N})** by {agent} — Code implemented, {n} files modified, {n} tests passed → {implementation-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` first):
 - Set `status: in-progress` and refine `in:` labels from the branch diff by following `.agents/rules/issue-sync.md` (add/remove when a mapping exists, add-only when it does not)

package/templates/.agents/skills/implement-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`：
@@ -91,7 +91,7 @@ date "+%Y-%m-%d %H:%M:%S"
 - 审查 `## 需求` 段落，仅把本轮已由代码实现且有测试通过支撑的条目从 `- [ ]` 勾为 `- [x]`
 - 记录 Round `{implementation-round}` 的 `{implementation-artifact}`
 - 追加：
-  `- {yyyy-MM-dd HH:mm:ss} — **Implementation (Round {N})** by {agent} — Code implemented, {n} files modified, {n} tests passed → {implementation-artifact}`
+  `- {YYYY-MM-DD HH:mm:ss±HH:MM} — **Implementation (Round {N})** by {agent} — Code implemented, {n} files modified, {n} tests passed → {implementation-artifact}`
 
 如果 task.md 中存在有效的 `issue_number`，执行以下同步操作（任一失败则跳过并继续；执行前先读取 `.agents/rules/issue-sync.md`）：
 - 设置 `status: in-progress`，并按 `.agents/rules/issue-sync.md` 的 `in:` label 同步规则，基于分支改动精修 `in:` label（有映射时可增可删，无映射时仅补充）

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

@@ -17,9 +17,7 @@ Import the specified Code Scanning (CodeQL) alert and create a remediation task.
 
 ### 1. Retrieve Alert Information
 
-```bash
-gh api repos/{owner}/{repo}/code-scanning/alerts/<alert-number>
-```
+Read `.agents/rules/security-alerts.md` before this step, then use its Code Scanning alert read command to fetch the alert details.
 
 Extract key information:
 - `number`: alert number
@@ -49,13 +47,13 @@ tool: <tool-name>
 Get the current time:
 
 ```bash
-date "+%Y-%m-%d %H:%M:%S"
+date "+%Y-%m-%d %H:%M:%S%:z"
 ```
 
 Update task.md: `current_step` -> `requirement-analysis`.
 - **Append** to `## Activity Log` (do NOT overwrite previous entries):
   ```
-  - {yyyy-MM-dd HH:mm:ss} — **Import Code Scanning Alert** by {agent} — Code Scanning alert #{alert-number} imported
+  - {YYYY-MM-DD HH:mm:ss±HH:MM} — **Import Code Scanning Alert** by {agent} — Code Scanning alert #{alert-number} imported
   ```
 
 ### 4. Verification Gate

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

@@ -17,9 +17,7 @@ description: "导入 Code Scanning 告警并创建修复任务"
 
 ### 1. 获取告警信息
 
-```bash
-gh api repos/{owner}/{repo}/code-scanning/alerts/<alert-number>
-```
+执行前先读取 `.agents/rules/security-alerts.md`，并按其中的 Code Scanning 告警读取命令获取告警详情。
 
 提取关键信息：
 - `number`：告警编号
@@ -49,13 +47,13 @@ tool: <tool-name>
 获取当前时间：
 
 ```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 Code Scanning Alert** by {agent} — Code Scanning alert #{alert-number} imported
+  - {YYYY-MM-DD HH:mm:ss±HH:MM} — **Import Code Scanning Alert** by {agent} — Code Scanning alert #{alert-number} imported
   ```
 
 ### 4. 完成校验

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

@@ -17,9 +17,7 @@ Import the specified Dependabot security alert and create a remediation task.
 
 ### 1. Retrieve Alert Information
 
-```bash
-gh api repos/{owner}/{repo}/dependabot/alerts/<alert-number>
-```
+Read `.agents/rules/security-alerts.md` before this step, then use its Dependabot alert read command to fetch the alert details.
 
 Extract key information:
 - `number`: alert number
@@ -50,13 +48,13 @@ ghsa_id: <GHSA-ID>
 Get the current time:
 
 ```bash
-date "+%Y-%m-%d %H:%M:%S"
+date "+%Y-%m-%d %H:%M:%S%:z"
 ```
 
 Update task.md: `current_step` -> `requirement-analysis`.
 - **Append** to `## Activity Log` (do NOT overwrite previous entries):
   ```
-  - {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. Verification Gate