@fitlab-ai/agent-infra 0.8.2 → 0.8.4

package/templates/.agents/skills/complete-manual-validation/config/verify.zh-CN.json

@@ -0,0 +1,49 @@
+{
+  "skill": "complete-manual-validation",
+  "checks": {
+    "task-meta": {
+      "required_fields": [
+        "id",
+        "type",
+        "workflow",
+        "status",
+        "created_at",
+        "updated_at",
+        "agent_infra_version",
+        "current_step",
+        "assigned_to"
+      ]
+    },
+    "artifact": {
+      "file_pattern": "manual-validation.md|manual-validation-r{N}.md",
+      "required_sections": [
+        "状态核对",
+        "验证结论",
+        "验证范围",
+        "验证详情",
+        "PR 摘要同步"
+      ],
+      "freshness_minutes": 30,
+      "required_patterns": [
+        "^\\$ "
+      ]
+    },
+    "activity-log": {
+      "expected_action_pattern": "Complete Manual Validation",
+      "freshness_minutes": 30
+    },
+    "review-ledger": {
+      "stage_scope": ["analysis", "plan", "code"]
+    },
+    "platform-sync": {
+      "when": "pr_number_exists",
+      "expected_pr_comment_marker_key": "prSummary",
+      "expected_pr_comment_required_patterns": [
+        "^### ✅ 人工验证已通过$"
+      ],
+      "verify_task_comment_content": true,
+      "verify_issue_type": true,
+      "verify_issue_fields": false
+    }
+  }
+}

package/templates/.agents/skills/complete-manual-validation/reference/report-template.en.md

@@ -0,0 +1,48 @@
+# Manual Validation Completion Report Template
+
+Read this file before creating `manual-validation.md` / `manual-validation-r{N}.md`.
+
+````markdown
+# Manual Validation Completion Report
+
+- **Validation Round**: Round {N}
+- **Artifact File**: `manual-validation.md`
+
+## State Check
+
+```text
+$ git status -s
+$ ls -la .agents/workspace/active/{task-id}/
+$ tail .agents/workspace/active/{task-id}/task.md
+```
+
+## Validation Verdict
+
+- Verdict: passed
+- Validation time: {YYYY-MM-DD HH:mm:ss±HH:MM}
+- Operator: {agent}
+
+## Validation Scope
+
+- PR: #{pr-number}
+- Summary comment: {comment-id or URL}
+- Manual-validation items:
+  - {item-1}
+
+## Validation Details
+
+{verification-summary}
+
+## PR Summary Sync
+
+- Result: {summary-result}
+- Summary comment: {comment-id or URL}
+- Updated status: `### ✅ Manual Validation Passed`
+````
+
+## Filling Rules
+
+- Keep `Validation Details` grounded in the user-provided validation notes.
+- Derive `Validation Scope` from the PR summary's manual-verification section.
+- `PR Summary Sync` must record success, skip, or failure.
+- Only write a passing artifact after the summary comment is updated or skipped because there is no diff.

package/templates/.agents/skills/complete-manual-validation/reference/report-template.zh-CN.md

@@ -0,0 +1,48 @@
+# 人工验证完成报告模板
+
+创建 `manual-validation.md` / `manual-validation-r{N}.md` 前先读取本文件。
+
+````markdown
+# 人工验证完成报告
+
+- **验证轮次**：Round {N}
+- **产物文件**：`manual-validation.md`
+
+## 状态核对
+
+```text
+$ git status -s
+$ ls -la .agents/workspace/active/{task-id}/
+$ tail .agents/workspace/active/{task-id}/task.md
+```
+
+## 验证结论
+
+- 结论：通过
+- 验证时间：{YYYY-MM-DD HH:mm:ss±HH:MM}
+- 执行者：{agent}
+
+## 验证范围
+
+- PR：#{pr-number}
+- 摘要评论：{comment-id 或 URL}
+- 待人工校验项：
+  - {item-1}
+
+## 验证详情
+
+{verification-summary}
+
+## PR 摘要同步
+
+- 结果：{summary-result}
+- 摘要评论：{comment-id 或 URL}
+- 更新状态：`### ✅ 人工验证已通过`
+````
+
+## 填写规则
+
+- `验证详情` 保留用户提供的人工验证说明，不改写成未经确认的结论。
+- `验证范围` 来自 PR 摘要评论中的 `### ⚠️ 需人工校验` 段。
+- `PR 摘要同步` 必须记录成功、跳过或失败结果。
+- 只有在摘要评论已成功更新或无 diff 跳过时，才写入通过产物。

package/templates/.agents/skills/complete-manual-validation/reference/summary-update.en.md

@@ -0,0 +1,60 @@
+# PR Summary Manual Validation Update
+
+Read this file before `complete-manual-validation` updates the PR summary comment.
+
+## Responsibility Boundary
+
+This file only describes PR summary comment updates. The manual-validation artifact schema lives in `reference/report-template.md`.
+
+## PR Number Resolution
+
+1. Resolve `{task-ref}` to the task directory and read `task.md`.
+2. Prefer `task.md` frontmatter `pr_number`.
+3. If `pr_number` is empty, parse `{pr-ref}` from user input: `#123`, `123`, or a full PR URL.
+4. If `task.md` already has `pr_number` and the user also passed `{pr-ref}`, they must match.
+5. If they differ, fail with `summary failed: pr_number mismatch`. Do not write an artifact or PATCH a comment.
+6. If both are missing, fail with `summary failed: missing pr_number`. Do not write an artifact or PATCH a comment.
+
+## Required Reads
+
+Before remote operations, read:
+- `.agents/rules/issue-sync.md` to resolve upstream repository and permissions.
+- `.agents/rules/pr-sync.md` to reuse the PR summary hidden marker, Issues comments API, and shell safety rules.
+
+## Comment Lookup
+
+Fetch ordinary PR comments with the current platform's Issues comments API. Follow the concrete command pattern in `.agents/rules/pr-sync.md`.
+
+Find the `<!-- sync-pr:{task-id}:summary -->` summary comment. If it is missing, fail with `summary failed: missing sync-pr summary`.
+
+On failure, do not create an ordinary validation comment, do not create a partial summary comment, and do not write a `manual-validation*` artifact.
+
+## Manual Validation Scope Extraction
+
+- If a `### ⚠️ Manual Verification Required` section exists, take that section until the next `### ` heading.
+- If the current summary already says `### ✅ Manual Validation Passed`, allow a new validation artifact round and update the details.
+- If the current summary says `### ✅ No Manual Verification Needed`, stop and report that this PR does not need manual validation; do not mark it as passed.
+
+## Three-Branch Rendering
+
+The updated `{manual-validation-section}` is:
+
+```markdown
+### ✅ Manual Validation Passed
+
+- Validation time: {time}
+- Validation notes: {verification-summary}
+```
+
+Later `pr-sync` aggregation renders in this priority order:
+1. latest `manual-validation.md` / `manual-validation-r{N}.md` has a passed verdict -> `### ✅ Manual Validation Passed`
+2. no passed artifact and retained manual-validation items exist -> `### ⚠️ Manual Verification Required`
+3. no passed artifact and no retained manual-validation items -> `### ✅ No Manual Verification Needed`
+
+## PATCH Rules
+
+Update existing comments with Issues comments PATCH and follow the heredoc safety rules in `.agents/rules/pr-sync.md`.
+
+## Result Reporting
+
+Return `summary updated`, `summary skipped (no diff)`, or `summary failed: <reason>`.

package/templates/.agents/skills/complete-manual-validation/reference/summary-update.zh-CN.md

@@ -0,0 +1,87 @@
+# PR 摘要人工验证更新
+
+在 `complete-manual-validation` 更新 PR 摘要评论前先读取本文件。
+
+## 职责边界
+
+本文件只描述 PR 摘要评论更新流程。人工验证产物结构见 `reference/report-template.md`。
+
+## PR 号解析
+
+1. 从 `{task-ref}` 定位任务目录并读取 `task.md`。
+2. 优先读取 `task.md` frontmatter 的 `pr_number`。
+3. 如果 `pr_number` 为空，再从用户输入的 `{pr-ref}` 解析：
+   - `#123`
+   - `123`
+   - `{platform-host}/{owner}/{repo}/pull/123`
+4. 如果 `task.md` 已有 `pr_number`，且用户也传入 `{pr-ref}`，两者必须一致。
+5. 两者不一致时失败：`summary failed: pr_number mismatch`。不写 artifact，不 PATCH 评论。
+6. 两者都缺失时失败：`summary failed: missing pr_number`。不写 artifact，不 PATCH 评论。
+
+## 前置读取
+
+执行远端操作前先读取：
+- `.agents/rules/issue-sync.md`，完成 upstream 仓库检测和权限检测。
+- `.agents/rules/pr-sync.md`，复用 PR 摘要隐藏标记、Issues comments API 和 Shell 安全规则。
+
+## 评论查找
+
+使用当前平台的 Issues comments API 查询 PR 上的普通评论，具体命令遵循 `.agents/rules/pr-sync.md`。
+
+查找以以下标记开头或包含该标记的评论：
+
+```html
+<!-- sync-pr:{task-id}:summary -->
+```
+
+找不到时失败：
+
+```text
+summary failed: missing sync-pr summary
+```
+
+失败时不创建普通验证留言，不创建部分摘要评论，不写 `manual-validation*` artifact。
+
+## 待人工校验范围提取
+
+从当前摘要评论中提取人工校验范围：
+- 如果存在 `### ⚠️ 需人工校验` 段，取该段到下一个 `### ` heading 之前的内容。
+- 如果当前摘要已是 `### ✅ 人工验证已通过`，允许再次写入新一轮验证产物并更新详情。
+- 如果当前摘要是 `### ✅ 无需人工校验`，停止并提示当前 PR 无需人工校验；不误标为人工验证已通过。
+
+## 三分支渲染
+
+更新后的 `{manual-validation-section}` 为：
+
+```markdown
+### ✅ 人工验证已通过
+
+- 验证时间：{time}
+- 验证说明：{verification-summary}
+```
+
+后续 `pr-sync` 聚合时按以下优先级渲染：
+1. 最新 `manual-validation.md` / `manual-validation-r{N}.md` 结论为通过 -> `### ✅ 人工验证已通过`
+2. 没有通过产物且仍有保留人工校验项 -> `### ⚠️ 需人工校验`
+3. 没有通过产物且无保留人工校验项 -> `### ✅ 无需人工校验`
+
+## PATCH 规则
+
+更新已有评论时必须使用 Issues comments PATCH，具体命令遵循 `.agents/rules/pr-sync.md`。
+
+Shell 安全规则：
+- 先读取本地和远端正文，再构造完整正文。
+- heredoc 使用单引号 `<<'EOF'`。
+- 不在 heredoc 内执行变量展开或命令替换。
+- 构造含 `<!-- -->` 的正文时不用 `echo`。
+
+## 结果回传
+
+返回以下结果之一：
+- `summary updated`
+- `summary skipped (no diff)`
+- `summary failed: missing pr_number`
+- `summary failed: pr_number mismatch`
+- `summary failed: missing sync-pr summary`
+- `summary failed: no manual validation required`
+- `summary failed: <reason>`

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

@@ -123,7 +123,7 @@ If prerequisites are not met and the user did not explicitly provide `--force`,
 Get the current time:
 
 ```bash
-date "+%Y-%m-%d %H:%M:%S%:z"
+date "+%Y-%m-%d %H:%M:%S%z" | sed 's/\([+-][0-9][0-9]\)\([0-9][0-9]\)$/\1:\2/'
 ```
 
 Update `.agents/workspace/active/{task-id}/task.md`:

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

@@ -122,7 +122,7 @@ Please complete the missing steps first, or use --force to override.
 获取当前时间：
 
 ```bash
-date "+%Y-%m-%d %H:%M:%S%:z"
+date "+%Y-%m-%d %H:%M:%S%z" | sed 's/\([+-][0-9][0-9]\)\([0-9][0-9]\)$/\1:\2/'
 ```
 
 更新 `.agents/workspace/active/{task-id}/task.md`：

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

@@ -41,7 +41,7 @@ Branch on the result:
 This project does not enable the PR flow (`.agents/.airc.json` sets `prFlow: "disabled"`).
 No Pull Request is required; run instead:
   - Claude Code / OpenCode: /complete-task {task-ref}
-  - Gemini CLI: /agent-infra:complete-task {task-ref}
+  - Gemini CLI: /{{project}}:complete-task {task-ref}
   - Codex CLI: $complete-task {task-ref}
 ```
 
@@ -105,7 +105,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%:z"
+date "+%Y-%m-%d %H:%M:%S%z" | sed 's/\([+-][0-9][0-9]\)\([0-9][0-9]\)$/\1:\2/'
 ```
 
 If `{task-id}` is available, update task.md with `pr_number`, `pr_status` (set to `created`), `updated_at`, `agent_infra_version`, and append the Create PR Activity Log entry including metadata-sync and summary results.
@@ -136,7 +136,7 @@ Explain the created PR URL, summarize metadata sync and summary-comment results,
 ```
 Next step - Watch PR checks (auto self-heal until required checks are green):
   - Claude Code / OpenCode: /watch-pr {task-ref}
-  - Gemini CLI: /agent-infra:watch-pr {task-ref}
+  - Gemini CLI: /{{project}}:watch-pr {task-ref}
   - Codex CLI: $watch-pr {task-ref}
 ```
 
@@ -145,7 +145,7 @@ Alternatively, to skip CI monitoring and archive the task right away, use `compl
 ```
 Next step (alternative) - Skip monitoring and archive the task directly:
   - Claude Code / OpenCode: /complete-task {task-ref}
-  - Gemini CLI: /agent-infra:complete-task {task-ref}
+  - Gemini CLI: /{{project}}:complete-task {task-ref}
   - Codex CLI: $complete-task {task-ref}
 ```
 
@@ -165,3 +165,5 @@ Next step (alternative) - Skip monitoring and archive the task directly:
 - Push rejected: suggest `git pull --rebase`
 - Existing PR found: show the current PR URL and stop
 - Inaccessible Issue metadata: skip inheritance and continue
+- PR creation failed with an associated `{task-id}`: run `node .agents/scripts/workflow-warnings.js add .agents/workspace/active/{task-id} --step create-pr --severity ACTION_REQUIRED --code PR_CREATE_FAILED --target pr --message "{reason}" --action "Fix push, permission, or platform issues and rerun create-pr"` and do not write `pr_number`
+- PR summary comment failed with an associated `{task-id}`: record a `COMMENT_SYNC_FAILED` warning per `.agents/rules/pr-sync.md`, without rolling back an already-created PR

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

@@ -41,7 +41,7 @@ description: >
 当前项目未启用 PR 流程（`.agents/.airc.json` 中 `prFlow: "disabled"`）。
 无需创建 Pull Request，请直接运行：
   - Claude Code / OpenCode：/complete-task {task-ref}
-  - Gemini CLI：/agent-infra:complete-task {task-ref}
+  - Gemini CLI：/{{project}}:complete-task {task-ref}
   - Codex CLI：$complete-task {task-ref}
 ```
 
@@ -105,7 +105,7 @@ description: >
 获取当前时间：
 
 ```bash
-date "+%Y-%m-%d %H:%M:%S%:z"
+date "+%Y-%m-%d %H:%M:%S%z" | sed 's/\([+-][0-9][0-9]\)\([0-9][0-9]\)$/\1:\2/'
 ```
 
 如果获取到了 `{task-id}`，更新 task.md 的 `pr_number`、`pr_status`（设为 `created`）、`updated_at`、`agent_infra_version`，并追加 Create PR 的 Activity Log，记录元数据同步和摘要发布结果。
@@ -136,7 +136,7 @@ node .agents/scripts/validate-artifact.js gate create-pr .agents/workspace/activ
 ```
 下一步 - 监控 PR 检查（required checks 全绿前自动自愈）：
   - Claude Code / OpenCode：/watch-pr {task-ref}
-  - Gemini CLI：/agent-infra:watch-pr {task-ref}
+  - Gemini CLI：/{{project}}:watch-pr {task-ref}
   - Codex CLI：$watch-pr {task-ref}
 ```
 
@@ -145,7 +145,7 @@ node .agents/scripts/validate-artifact.js gate create-pr .agents/workspace/activ
 ```
 下一步（备选）- 跳过监控、直接归档任务：
   - Claude Code / OpenCode：/complete-task {task-ref}
-  - Gemini CLI：/agent-infra:complete-task {task-ref}
+  - Gemini CLI：/{{project}}:complete-task {task-ref}
   - Codex CLI：$complete-task {task-ref}
 ```
 
@@ -165,3 +165,5 @@ node .agents/scripts/validate-artifact.js gate create-pr .agents/workspace/activ
 - 推送被拒绝：建议执行 `git pull --rebase`
 - 已存在 PR：直接输出当前 PR URL 并结束
 - 无法访问 Issue 元数据：跳过继承并继续
+- PR 创建失败且已关联 `{task-id}`：调用 `node .agents/scripts/workflow-warnings.js add .agents/workspace/active/{task-id} --step create-pr --severity ACTION_REQUIRED --code PR_CREATE_FAILED --target pr --message "{reason}" --action "修复推送、权限或平台问题后重跑 create-pr"`，不写 `pr_number`
+- PR 摘要评论失败且已关联 `{task-id}`：按 `.agents/rules/pr-sync.md` 记录 `COMMENT_SYNC_FAILED` 告警，不回滚已创建 PR

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

@@ -70,6 +70,6 @@ Final user output should include this follow-up path:
 Next steps:
   - complete the task after the workflow truly finishes:
     - Claude Code / OpenCode: /complete-task {task-ref}
-    - Gemini CLI: /agent-infra:complete-task {task-ref}
+    - Gemini CLI: /{{project}}:complete-task {task-ref}
     - Codex CLI: $complete-task {task-ref}
 ```

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

@@ -70,6 +70,6 @@ Milestone 规则：
 Next steps:
   - complete the task after the workflow truly finishes:
     - Claude Code / OpenCode: /complete-task {task-ref}
-    - Gemini CLI: /agent-infra:complete-task {task-ref}
+    - Gemini CLI: /{{project}}:complete-task {task-ref}
     - Codex CLI: $complete-task {task-ref}
 ```

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

@@ -30,7 +30,7 @@ Version stamp rule: when creating or updating `task.md` frontmatter, read `.agen
 
 ## Step Start: Capture the Start Time
 
-This skill **creates** task.md, so there is no file to write at the start. Capture `started_at` in memory before running (`date "+%Y-%m-%d %H:%M:%S%:z"`); when writing the Activity Log at the end, **append both lines at once** — the started line uses `started_at`, the done line uses the completion time, both sharing the base action (started line action gets a ` [started]` suffix, note `started`):
+This skill **creates** task.md, so there is no file to write at the start. Capture `started_at` in memory before running (`date "+%Y-%m-%d %H:%M:%S%z" | sed 's/\([+-][0-9][0-9]\)\([0-9][0-9]\)$/\1:\2/'`); when writing the Activity Log at the end, **append both lines at once** — the started line uses `started_at`, the done line uses the completion time, both sharing the base action (started line action gets a ` [started]` suffix, note `started`):
 
 ```
 - {started_at} — **Create Task [started]** by {agent} — started
@@ -109,7 +109,7 @@ priority / effort are required: the AI infers them from the task title and descr
 Get the current time:
 
 ```bash
-date "+%Y-%m-%d %H:%M:%S%:z"
+date "+%Y-%m-%d %H:%M:%S%z" | sed 's/\([+-][0-9][0-9]\)\([0-9][0-9]\)$/\1:\2/'
 ```
 
 Update `.agents/workspace/active/{task-id}/task.md`:
@@ -135,7 +135,7 @@ The rule's content is determined by the configured code platform:
 
 Handle the result:
 - Rule successfully created the Issue: `issue_number` has been written back to task.md per the rule; continue by reading `.agents/rules/issue-sync.md`, completing upstream repository and permission detection, then sync the task comment and set `status: waiting-for-triage` by rule
-- Rule failed (auth / network / template parse / etc.): do not roll back task.md; do NOT append an extra Activity Log entry; follow "Scenario C: Issue creation failed" output to surface `error_code` and `error_message` to the user so they can decide whether to retry manually or write `issue_number` later
+- Rule failed (auth / network / template parse / etc.): do not roll back task.md; do NOT append an extra Activity Log entry; first run `node .agents/scripts/workflow-warnings.js add .agents/workspace/active/{task-id} --step create-task --severity ACTION_REQUIRED --code ISSUE_CREATE_FAILED --target issue --message "{error_code}: {error_message}" --action "Fix auth/network/template issues and manually retry Issue creation, or create/find an Issue and write issue_number"` to record a generic warning; then follow "Scenario C: Issue creation failed" output to surface `error_code` and `error_message`
 - Rule was a no-op (custom or empty platform): do not create comments, do not block the workflow, and do not write an Activity Log entry
 - task.md already has `issue_number`: the rule's prerequisite check skips creation; `create-task` proceeds directly to step 5
 
@@ -231,6 +231,9 @@ Next step - run requirements analysis:
   - Codex CLI: $analyze-task {task-ref}
 
 For later platform sync: after fixing auth / network / template issues, manually run the Issue creation flow in `.agents/rules/create-issue.md` for this task; or manually create/find an Issue and write `issue_number` into task.md so later skills can take over cascade sync.
+
+[ACTION REQUIRED] Workflow warnings are open:
+  - WW-N ISSUE_CREATE_FAILED (issue): Fix auth/network/template issues and manually retry Issue creation, or create/find an Issue and write issue_number
 ```
 
 

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

@@ -30,7 +30,7 @@ description: >
 
 ## 步骤开始：记录开始时间
 
-本技能会**创建** task.md，开始时尚无文件可写。先在内存记录开始时间 `started_at`（`date "+%Y-%m-%d %H:%M:%S%:z"`）；在最后写活动日志时**一次性补两条**——started 行用 `started_at`、done 行用完成时间，二者同基名（started 行 action 加 ` [started]` 后缀、note 用 `started`）：
+本技能会**创建** task.md，开始时尚无文件可写。先在内存记录开始时间 `started_at`（`date "+%Y-%m-%d %H:%M:%S%z" | sed 's/\([+-][0-9][0-9]\)\([0-9][0-9]\)$/\1:\2/'`）；在最后写活动日志时**一次性补两条**——started 行用 `started_at`、done 行用完成时间，二者同基名（started 行 action 加 ` [started]` 后缀、note 用 `started`）：
 
 ```
 - {started_at} — **Create Task [started]** by {agent} — started
@@ -108,7 +108,7 @@ priority / effort 必填：由 AI 从任务标题与描述推断后填入（候
 获取当前时间：
 
 ```bash
-date "+%Y-%m-%d %H:%M:%S%:z"
+date "+%Y-%m-%d %H:%M:%S%z" | sed 's/\([+-][0-9][0-9]\)\([0-9][0-9]\)$/\1:\2/'
 ```
 
 更新 `.agents/workspace/active/{task-id}/task.md`：
@@ -134,7 +134,7 @@ date "+%Y-%m-%d %H:%M:%S%:z"
 
 处理结果：
 - 规则成功创建 Issue：`issue_number` 已按规则回写到 task.md；继续读取 `.agents/rules/issue-sync.md`，完成 upstream 仓库检测和权限检测，然后同步 task 评论并按规则设置 `status: waiting-for-triage`
-- 规则失败（认证 / 网络 / 模板解析等）：不回滚 task.md；不追加额外 Activity Log；按"场景 C：Issue 创建失败"输出向用户透出 `error_code` 与 `error_message`，让用户决定后续是否手动重试或写入 `issue_number`
+- 规则失败（认证 / 网络 / 模板解析等）：不回滚 task.md；不追加额外 Activity Log；先调用 `node .agents/scripts/workflow-warnings.js add .agents/workspace/active/{task-id} --step create-task --severity ACTION_REQUIRED --code ISSUE_CREATE_FAILED --target issue --message "{error_code}: {error_message}" --action "修复认证/网络/模板问题后手动重试 Issue 创建，或手动创建/找到 Issue 后写入 issue_number"` 记录通用告警；再按"场景 C：Issue 创建失败"输出向用户透出 `error_code` 与 `error_message`
 - 规则为 no-op（自定义或空平台）：不创建评论，不阻塞后续工作流，不写 Activity Log
 - task.md 已存在 `issue_number`：规则中的前置检查会跳过；`create-task` 直接进入步骤 5
 
@@ -183,7 +183,7 @@ node .agents/scripts/validate-artifact.js gate create-task .agents/workspace/act
 
 下一步 - 执行需求分析：
   - Claude Code / OpenCode：/analyze-task {task-ref}
-  - Gemini CLI：/agent-infra:analyze-task {task-ref}
+  - Gemini CLI：/{{project}}:analyze-task {task-ref}
   - Codex CLI：$analyze-task {task-ref}
 ```
 
@@ -202,7 +202,7 @@ node .agents/scripts/validate-artifact.js gate create-task .agents/workspace/act
 
 下一步 - 执行需求分析：
   - Claude Code / OpenCode：/analyze-task {task-ref}
-  - Gemini CLI：/agent-infra:analyze-task {task-ref}
+  - Gemini CLI：/{{project}}:analyze-task {task-ref}
   - Codex CLI：$analyze-task {task-ref}
 ```
 
@@ -226,10 +226,13 @@ Issue 创建失败：
 
 下一步 - 执行需求分析：
   - Claude Code / OpenCode：/analyze-task {task-ref}
-  - Gemini CLI：/agent-infra:analyze-task {task-ref}
+  - Gemini CLI：/{{project}}:analyze-task {task-ref}
   - Codex CLI：$analyze-task {task-ref}
 
 后续如需平台同步：修复认证/网络/模板问题后，可按 `.agents/rules/create-issue.md` 对当前任务手动执行一次 Issue 创建；或手动创建/查找 Issue，并把 `issue_number` 写入 task.md，后续技能会接管级联同步。
+
+[ACTION REQUIRED] Workflow warnings are open:
+  - WW-N ISSUE_CREATE_FAILED (issue): 修复认证/网络/模板问题后手动重试 Issue 创建，或手动创建/找到 Issue 后写入 issue_number
 ```
 
 

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

@@ -21,7 +21,7 @@ Import the specified Code Scanning (CodeQL) alert and create a remediation task.
 
 ## Step Start: Capture the Start Time
 
-This skill **creates** task.md, so there is no file to write at the start. Capture `started_at` in memory before running (`date "+%Y-%m-%d %H:%M:%S%:z"`); when writing the Activity Log at the end, **append both lines at once** — the started line uses `started_at`, the done line uses the completion time, both sharing the base action (started line action gets a ` [started]` suffix, note `started`):
+This skill **creates** task.md, so there is no file to write at the start. Capture `started_at` in memory before running (`date "+%Y-%m-%d %H:%M:%S%z" | sed 's/\([+-][0-9][0-9]\)\([0-9][0-9]\)$/\1:\2/'`); when writing the Activity Log at the end, **append both lines at once** — the started line uses `started_at`, the done line uses the completion time, both sharing the base action (started line action gets a ` [started]` suffix, note `started`):
 
 ```
 - {started_at} — **Import Codescan [started]** by {agent} — started
@@ -61,7 +61,7 @@ codescan_alert_number: <alert-number>
 Get the current time:
 
 ```bash
-date "+%Y-%m-%d %H:%M:%S%:z"
+date "+%Y-%m-%d %H:%M:%S%z" | sed 's/\([+-][0-9][0-9]\)\([0-9][0-9]\)$/\1:\2/'
 ```
 
 Update task.md: `current_step` -> `requirement-analysis`.

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

@@ -21,7 +21,7 @@ description: >
 
 ## 步骤开始：记录开始时间
 
-本技能会**创建** task.md，开始时尚无文件可写。先在内存记录开始时间 `started_at`（`date "+%Y-%m-%d %H:%M:%S%:z"`）；在最后写活动日志时**一次性补两条**——started 行用 `started_at`、done 行用完成时间，二者同基名（started 行 action 加 ` [started]` 后缀、note 用 `started`）：
+本技能会**创建** task.md，开始时尚无文件可写。先在内存记录开始时间 `started_at`（`date "+%Y-%m-%d %H:%M:%S%z" | sed 's/\([+-][0-9][0-9]\)\([0-9][0-9]\)$/\1:\2/'`）；在最后写活动日志时**一次性补两条**——started 行用 `started_at`、done 行用完成时间，二者同基名（started 行 action 加 ` [started]` 后缀、note 用 `started`）：
 
 ```
 - {started_at} — **Import Codescan [started]** by {agent} — started
@@ -61,7 +61,7 @@ codescan_alert_number: <alert-number>
 获取当前时间：
 
 ```bash
-date "+%Y-%m-%d %H:%M:%S%:z"
+date "+%Y-%m-%d %H:%M:%S%z" | sed 's/\([+-][0-9][0-9]\)\([0-9][0-9]\)$/\1:\2/'
 ```
 
 更新 task.md：`current_step` -> `requirement-analysis`。
@@ -112,7 +112,7 @@ Code Scanning 告警 #{alert-number} 已导入。
 
 下一步：
   - Claude Code / OpenCode：/analyze-task {task-ref}
-  - Gemini CLI：/agent-infra:analyze-task {task-ref}
+  - Gemini CLI：/{{project}}:analyze-task {task-ref}
   - Codex CLI：$analyze-task {task-ref}
 ```
 

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

@@ -21,7 +21,7 @@ Import the specified Dependabot security alert and create a remediation task.
 
 ## Step Start: Capture the Start Time
 
-This skill **creates** task.md, so there is no file to write at the start. Capture `started_at` in memory before running (`date "+%Y-%m-%d %H:%M:%S%:z"`); when writing the Activity Log at the end, **append both lines at once** — the started line uses `started_at`, the done line uses the completion time, both sharing the base action (started line action gets a ` [started]` suffix, note `started`):
+This skill **creates** task.md, so there is no file to write at the start. Capture `started_at` in memory before running (`date "+%Y-%m-%d %H:%M:%S%z" | sed 's/\([+-][0-9][0-9]\)\([0-9][0-9]\)$/\1:\2/'`); when writing the Activity Log at the end, **append both lines at once** — the started line uses `started_at`, the done line uses the completion time, both sharing the base action (started line action gets a ` [started]` suffix, note `started`):
 
 ```
 - {started_at} — **Import Dependabot [started]** by {agent} — started
@@ -64,7 +64,7 @@ ghsa_id: <GHSA-ID>
 Get the current time:
 
 ```bash
-date "+%Y-%m-%d %H:%M:%S%:z"
+date "+%Y-%m-%d %H:%M:%S%z" | sed 's/\([+-][0-9][0-9]\)\([0-9][0-9]\)$/\1:\2/'
 ```
 
 Update task.md: `current_step` -> `requirement-analysis`.

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

@@ -21,7 +21,7 @@ description: >
 
 ## 步骤开始：记录开始时间
 
-本技能会**创建** task.md，开始时尚无文件可写。先在内存记录开始时间 `started_at`（`date "+%Y-%m-%d %H:%M:%S%:z"`）；在最后写活动日志时**一次性补两条**——started 行用 `started_at`、done 行用完成时间，二者同基名（started 行 action 加 ` [started]` 后缀、note 用 `started`）：
+本技能会**创建** task.md，开始时尚无文件可写。先在内存记录开始时间 `started_at`（`date "+%Y-%m-%d %H:%M:%S%z" | sed 's/\([+-][0-9][0-9]\)\([0-9][0-9]\)$/\1:\2/'`）；在最后写活动日志时**一次性补两条**——started 行用 `started_at`、done 行用完成时间，二者同基名（started 行 action 加 ` [started]` 后缀、note 用 `started`）：
 
 ```
 - {started_at} — **Import Dependabot [started]** by {agent} — started
@@ -64,7 +64,7 @@ ghsa_id: <GHSA-ID>
 获取当前时间：
 
 ```bash
-date "+%Y-%m-%d %H:%M:%S%:z"
+date "+%Y-%m-%d %H:%M:%S%z" | sed 's/\([+-][0-9][0-9]\)\([0-9][0-9]\)$/\1:\2/'
 ```
 
 更新 task.md：`current_step` -> `requirement-analysis`。
@@ -118,7 +118,7 @@ node .agents/scripts/validate-artifact.js gate import-dependabot .agents/workspa
 
 下一步：
   - Claude Code / OpenCode：/analyze-task {task-ref}
-  - Gemini CLI：/agent-infra:analyze-task {task-ref}
+  - Gemini CLI：/{{project}}:analyze-task {task-ref}
   - Codex CLI：$analyze-task {task-ref}
 ```
 

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

@@ -21,7 +21,7 @@ Import the specified Issue and create a task. Argument: issue number.
 
 ## Step Start: Capture the Start Time
 
-This skill **creates** task.md, so there is no file to write at the start. Capture `started_at` in memory before running (`date "+%Y-%m-%d %H:%M:%S%:z"`); when writing the Activity Log at the end, **append both lines at once** — the started line uses `started_at`, the done line uses the completion time, both sharing the base action (started line action gets a ` [started]` suffix, note `started`). The base action must match the actual import scenario:
+This skill **creates** task.md, so there is no file to write at the start. Capture `started_at` in memory before running (`date "+%Y-%m-%d %H:%M:%S%z" | sed 's/\([+-][0-9][0-9]\)\([0-9][0-9]\)$/\1:\2/'`); when writing the Activity Log at the end, **append both lines at once** — the started line uses `started_at`, the done line uses the completion time, both sharing the base action (started line action gets a ` [started]` suffix, note `started`). The base action must match the actual import scenario:
 
 ```
 # Scenario B: new Issue import
@@ -127,7 +127,7 @@ Optional Issue field metadata should preserve recovered or explicit source value
 Get the current time:
 
 ```bash
-date "+%Y-%m-%d %H:%M:%S%:z"
+date "+%Y-%m-%d %H:%M:%S%z" | sed 's/\([+-][0-9][0-9]\)\([0-9][0-9]\)$/\1:\2/'
 ```
 
 Update `.agents/workspace/active/{task-id}/task.md`: