@fitlab-ai/agent-infra 0.5.7 → 0.5.9

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

@@ -61,7 +61,7 @@ Confirm? (y/N)
 
 Dismiss the alert by following the Code Scanning dismiss command in `.agents/rules/security-alerts.md`, passing the mapped `{api-reason}` and the user's explanation.
 
-**API reason mapping** (per the GitHub Code Scanning API):
+**API reason mapping** (per the Code Scanning API):
 - False Positive -> `false positive`
 - Won't Fix -> `won't fix`
 - Used in Tests -> `used in tests`
@@ -96,7 +96,7 @@ Explanation: {explanation}
 
 View: {html_url}
 
-Note: it can be reopened on GitHub if necessary.
+Note: it can be reopened on the platform if necessary.
 
 Next step - complete and archive the task if a related task exists:
   - Claude Code / OpenCode: /complete-task {task-id}

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

@@ -61,7 +61,7 @@ Code Scanning 告警 #{alert-number}
 
 按 `.agents/rules/security-alerts.md` 中的 Code Scanning 告警关闭命令执行关闭操作，并传入映射后的 `{api-reason}` 与用户说明。
 
-**API reason 映射**（按 GitHub Code Scanning API）：
+**API reason 映射**（按 Code Scanning API）：
 - 误报 -> `false positive`
 - 不会修复 -> `won't fix`
 - 测试代码 -> `used in tests`
@@ -96,7 +96,7 @@ Code Scanning 告警 #{alert-number} 已关闭。
 
 查看：{html_url}
 
-注意：如有需要，可在 GitHub 上重新打开。
+注意：如有需要，可在 平台上重新打开。
 
 下一步 - 完成并归档任务（如有关联任务）：
   - Claude Code / OpenCode：/complete-task {task-id}

package/templates/.agents/skills/commit/SKILL.en.md

@@ -64,7 +64,7 @@ Failure handling matches "Update Task Status When Applicable": warn, but do **no
 
 ## 7. Sync PR Summary When Applicable
 
-When `{task-id}` exists and task.md contains a valid `pr_number`, refresh the PR summary comment `<!-- sync-pr:{task-id}:summary -->` on the PR. Otherwise, skip this step.
+When `{task-id}` exists and task.md contains a valid `pr_number`, refresh the PR summary comment marked with the PR summary marker defined in `.agents/rules/pr-sync.md` on the PR. Otherwise, skip this step.
 
 > The full trigger conditions, aggregation rules, PATCH/POST flow, shell-safety constraints, and error handling live in `reference/pr-summary-sync.md` (which in turn points to `.agents/rules/pr-sync.md`). Read `reference/pr-summary-sync.md` before executing this step.
 >

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

@@ -64,7 +64,7 @@ date "+%Y-%m-%d %H:%M:%S%:z"
 
 ## 7. 同步 PR 摘要（按需）
 
-当 `{task-id}` 存在且 task.md 包含有效 `pr_number` 时，刷新 PR 上的 `<!-- sync-pr:{task-id}:summary -->` 摘要评论；否则跳过。
+当 `{task-id}` 存在且 task.md 包含有效 `pr_number` 时，刷新 PR 上由 `.agents/rules/pr-sync.md` 中定义的 PR 摘要评论标记对应的摘要评论；否则跳过。
 
 > 完整的触发条件、聚合规则、PATCH/POST 流程、Shell 安全约束和错误处理见 `reference/pr-summary-sync.md`（其内联引用 `.agents/rules/pr-sync.md`）。执行此步骤前先读取 `reference/pr-summary-sync.md`。
 >

package/templates/.agents/skills/commit/config/verify.json

@@ -21,7 +21,8 @@
       "when": "pr_number_exists",
       "expected_pr_comment_marker": "<!-- sync-pr:{task-id}:summary -->",
       "verify_in_labels_computed": true,
-      "verify_pr_comment_last_commit_matches_head": true
+      "verify_pr_comment_last_commit_matches_head": true,
+      "expected_pr_comment_marker_key": "prSummary"
     }
   }
 }

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

@@ -93,7 +93,7 @@ If a valid `issue_number` exists:
 - First scan and backfill unpublished `task.md`, `analysis*.md`, `plan*.md`, `implementation*.md`, `review*.md`, and `refinement*.md` comments using the backfill rules in `.agents/rules/issue-sync.md` (`task.md` uses the idempotent update path)
 - Backfill checked `## Requirements` items to the Issue body by following the requirements-checkbox sync steps in issue-sync.md
 - Do not set any `status:` label — status labels are automatically cleared when the Issue is closed
-- Finally create or update the summary comment marked with `<!-- sync-issue:{task-id}:summary -->`
+- Finally create or update the summary comment marked with the summary marker defined in `.agents/rules/issue-sync.md`
 
 ### 7. Verification Gate
 

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

@@ -93,7 +93,7 @@ ls .agents/workspace/completed/{task-id}/task.md
 - 先按 `.agents/rules/issue-sync.md` 的补发规则扫描并补发未发布的 `task.md`、`analysis*.md`、`plan*.md`、`implementation*.md`、`review*.md`、`refinement*.md` 评论（`task.md` 走幂等更新路径）
 - 按 issue-sync.md 的需求复选框同步步骤，兜底同步 `## 需求` 中已勾选的条目到 Issue body
 - 不要设置 `status:` label — Issue 关闭后 status label 会被自动清除
-- 最后创建或更新 `<!-- sync-issue:{task-id}:summary -->` 标记的 summary 评论
+- 最后创建或更新 `.agents/rules/issue-sync.md` 中定义的 summary 评论标记对应的 summary 评论
 
 ### 7. 完成校验
 

package/templates/.agents/skills/complete-task/config/verify.json

@@ -29,7 +29,8 @@
       "verify_task_comment_content": true,
       "sync_checked_requirements": true,
       "verify_issue_type": true,
-      "verify_milestone": true
+      "verify_milestone": true,
+      "expected_comment_marker_key": "summary"
     }
   }
 }

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

@@ -26,7 +26,7 @@ Use the explicit argument when provided. Otherwise infer the target branch from
 
 ### 3. Prepare the PR Body
 
-Read `.github/PULL_REQUEST_TEMPLATE.md` when it exists, review recent merged PRs for style, and gather all commits between `<target-branch>` and `HEAD`.
+Read the PR template through `.agents/rules/issue-pr-commands.md`, review recent merged PRs for style, and gather all commits between `<target-branch>` and `HEAD`.
 
 > Template handling, HEREDOC body generation, and `Generated with AI assistance` requirements live in `reference/pr-body-template.md`. Read `reference/pr-body-template.md` before writing the PR body.
 
@@ -101,7 +101,7 @@ Explain the created PR URL, summarize metadata sync and summary-comment results,
 
 - Review every commit in the branch, not only the latest one
 - `create-pr` must not defer type-label mapping to another skill; inline the mapping here when `{task-id}` is available
-- Keep the hidden summary marker as `<!-- sync-pr:{task-id}:summary -->` for compatibility with existing PR comments
+- Keep the hidden summary marker as the PR summary marker defined in `.agents/rules/pr-sync.md` for compatibility with existing PR comments
 - If the current branch already has a PR, show its URL and stop without repeating sync work
 - When metadata inheritance from the Issue fails, continue with task.md and branch-based fallbacks
 

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

@@ -26,7 +26,7 @@ description: "创建 Pull Request 到目标分支"
 
 ### 3. 准备 PR 正文
 
-读取 `.github/PULL_REQUEST_TEMPLATE.md`（如存在），参考最近合并的 PR 风格，并收集 `<target-branch>` 到 `HEAD` 的全部提交。
+通过 `.agents/rules/issue-pr-commands.md` 读取 PR 模板，参考最近合并的 PR 风格，并收集 `<target-branch>` 到 `HEAD` 的全部提交。
 
 > 模板处理、HEREDOC 正文生成和 `Generated with AI assistance` 要求见 `reference/pr-body-template.md`。编写正文前先读取 `reference/pr-body-template.md`。
 
@@ -101,7 +101,7 @@ node .agents/scripts/validate-artifact.js gate create-pr .agents/workspace/activ
 
 - 必须检查分支中的全部提交，而不是只看最后一个
 - `create-pr` 不能把 type label 映射委托给其他技能，必须在获取到 `{task-id}` 时于本技能内内联处理
-- 隐藏 summary 标记必须保持 `<!-- sync-pr:{task-id}:summary -->` 以兼容已有 PR 评论
+- 隐藏 summary 标记必须保持为 `.agents/rules/pr-sync.md` 中定义的 PR 摘要评论标记，以兼容已有 PR 评论
 - 如果当前分支已存在 PR，直接告知用户 PR URL 并结束，不做重复同步
 - 如果从 Issue 继承元数据失败，继续使用 task.md 和分支推断兜底
 

package/templates/.agents/skills/create-pr/config/verify.json

@@ -23,7 +23,8 @@
       "verify_in_labels_match_pr": true,
       "verify_pr_type_label": true,
       "verify_pr_assignee": true,
-      "verify_milestone": true
+      "verify_milestone": true,
+      "expected_pr_comment_marker_key": "prSummary"
     }
   }
 }

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

@@ -4,15 +4,11 @@ Read this file before generating the PR title and body.
 
 ## Read the PR Template
 
-Read `.github/PULL_REQUEST_TEMPLATE.md` from the repository. If it does not exist, use the standard format.
+PR template discovery is platform-specific. Read `.agents/rules/issue-pr-commands.md` and follow the PR template section provided by the configured platform. If no template is available, use the standard format.
 
 ## Review Recent Merged PRs for Reference
 
-```bash
-gh pr list --limit 3 --state merged --json number,title,body
-```
-
-Use the recent merged PRs as style and formatting references.
+Use the recent merged PR query from `.agents/rules/issue-pr-commands.md` as style and formatting reference input.
 
 ## Analyze Current Branch Changes
 
@@ -27,19 +23,13 @@ git diff <target-branch>...HEAD
 
 Read `.agents/rules/issue-pr-commands.md` before this step.
 
-Before syncing linked Issue metadata, complete authentication and code-hosting platform detection through that rule. Keep `gh pr list` / `gh pr create` on the current repository.
-
-Before syncing labels, verify the standard label system:
-
-```bash
-gh label list --search "type:" --limit 1 --json name --jq 'length'
-```
+Before syncing linked Issue metadata, complete authentication and code-hosting platform detection through that rule.
 
-If the result is `0`, run `init-labels` before retrying metadata sync.
+Before syncing labels, verify the standard label system by following the label-list command in `.agents/rules/issue-pr-commands.md`. If the result shows no standard type labels, run `init-labels` before retrying metadata sync.
 
 Type label mapping:
 
-| task.md type | GitHub label |
+| task.md type | label |
 |---|---|
 | `bug`, `bugfix` | `type: bug` |
 | `feature` | `type: feature` |
@@ -54,7 +44,7 @@ Metadata sync order:
 1. query Issue labels and milestone via the Issue read command in `.agents/rules/issue-pr-commands.md`
 2. build `{label-args}` from the mapped type label, non-`type:` / non-`status:` Issue labels, and the current Issue `in:` labels (commit already computed them, so do not recompute them here and do not write back to the Issue)
 3. build `{milestone-arg}` by following "Phase 3: `create-pr`" in `.agents/rules/milestone-inference.md` and reusing the Issue milestone directly
-4. pass `{label-args}` and `{milestone-arg}` atomically to `gh pr create` by using the create-PR command template and permission-degradation rules in `.agents/rules/issue-pr-commands.md`
+4. pass `{label-args}` and `{milestone-arg}` atomically by using the create-PR command template and permission-degradation rules in `.agents/rules/issue-pr-commands.md`
 5. ensure the PR body contains `Closes #{issue-number}` or an equivalent closing keyword
 
 If those rules say to skip the direct metadata arguments above, keep only the PR body linkage plus later comment sync.
@@ -72,7 +62,7 @@ Milestone rule:
 - Replace `{$IssueNumber}` in the template when present
 - End the PR body with `Generated with AI assistance`
 
-Create the PR with the "Create a PR" command template in `.agents/rules/issue-pr-commands.md`.
+Create the PR with the create-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

@@ -1,20 +1,16 @@
 # PR 正文模板规则
 
-在生成 PR 标题和正文之前先读取本文件。
+生成 PR 标题和正文前先读取本文件。
 
 ## 读取 PR 模板
 
-读取仓库中的 `.github/PULL_REQUEST_TEMPLATE.md`。如果不存在，则使用标准格式。
+PR 模板发现属于平台相关逻辑。先读取 `.agents/rules/issue-pr-commands.md`，并按当前配置平台提供的 PR 模板章节执行。如果没有可用模板，则使用标准格式。
 
 ## 参考最近合并的 PR
 
-```bash
-gh pr list --limit 3 --state merged --json number,title,body
-```
+使用 `.agents/rules/issue-pr-commands.md` 中的最近合并 PR 查询命令，作为风格和格式参考输入。
 
-把最近合并的 PR 当作风格和排版参考。
-
-## 分析当前分支变更
+## 分析当前分支改动
 
 ```bash
 git status
@@ -25,21 +21,15 @@ git diff <target-branch>...HEAD
 
 ## 同步 PR 元数据
 
-执行前先读取 `.agents/rules/issue-pr-commands.md`。
-
-同步关联 Issue 元数据前，先按该规则完成认证和代码托管平台检测；`gh pr list` / `gh pr create` 仍保持作用于当前仓库。
+执行本步骤前先读取 `.agents/rules/issue-pr-commands.md`。
 
-在同步 label 之前，先确认标准 label 体系已经存在：
-
-```bash
-gh label list --search "type:" --limit 1 --json name --jq 'length'
-```
+同步关联 Issue 元数据前，先按该规则完成认证和代码托管平台检测。
 
-如果结果是 `0`，先执行 `init-labels`，再重试元数据同步。
+同步 label 前，按 `.agents/rules/issue-pr-commands.md` 中的 label 列表命令验证标准 label 体系。如果结果显示没有标准 type label，先运行 `init-labels` 再重试元数据同步。
 
-Type label 映射：
+类型 label 映射：
 
-| task.md type | GitHub label |
+| task.md type | label |
 |---|---|
 | `bug`, `bugfix` | `type: bug` |
 | `feature` | `type: feature` |
@@ -51,34 +41,34 @@ Type label 映射：
 | 其他值 | 跳过 |
 
 元数据同步顺序：
-1. 按 `.agents/rules/issue-pr-commands.md` 的 Issue 读取命令查询关联 Issue 的 labels 和 milestone
-2. 构建 `{label-args}`：包含映射后的 type label、非 `type:`/`status:` 的 Issue labels，以及 Issue 当前的 `in:` labels（commit 阶段已完成计算，此处不重新计算也不反向更新 Issue）
-3. 构建 `{milestone-arg}`：按 `.agents/rules/milestone-inference.md` 的「阶段 3：`create-pr`」直接复用 Issue milestone
-4. 按 `.agents/rules/issue-pr-commands.md` 的创建 PR 命令模板与权限降级规则，将 `{label-args}` 和 `{milestone-arg}` 原子化传入 `gh pr create`
-5. 确保 PR 正文包含 `Closes #{issue-number}` 或等价的 closing keyword
+1. 通过 `.agents/rules/issue-pr-commands.md` 的 Issue 读取命令查询 Issue labels 和 milestone
+2. 从映射出的 type label、非 `type:` / 非 `status:` 的 Issue labels，以及当前 Issue `in:` labels 构建 `{label-args}`（commit 已经计算过，不在此重算，也不写回 Issue）
+3. 按 `.agents/rules/milestone-inference.md` 的 "阶段 3：`create-pr`" 复用 Issue milestone 构建 `{milestone-arg}`
+4. 按 `.agents/rules/issue-pr-commands.md` 的创建 PR 命令模板与权限降级规则，将 `{label-args}` 和 `{milestone-arg}` 原子化传入
+5. 确保 PR 正文包含 `Closes #{issue-number}` 或等价关闭关键字
 
-如果上述规则判定应跳过直接元数据参数写入，则只保留 PR 正文中的关联信息与后续评论同步。
+如果规则要求跳过上述直接元数据参数，则只保留 PR 正文关联和后续评论同步。
 
 Milestone 规则：
-- 按 `.agents/rules/milestone-inference.md` 的「阶段 3：`create-pr`」处理
-- PR 直接复用 Issue milestone，不再独立推断
+- 按 `.agents/rules/milestone-inference.md` 的 "阶段 3：`create-pr`" 执行
+- 直接复用关联 Issue 的 milestone，不为 PR 重新推断
 
 ## 创建 PR
 
-- 当当前工作属于活动任务时，从 task.md 中提取 `issue_number`
-- 如果存在 `issue_number`，先完成前置步骤中的代码托管平台检测，再按 `.agents/rules/issue-pr-commands.md` 的 Issue 读取命令查询对应 Issue
-- 在调用 PR 创建命令前，先检查当前分支是否已经存在 PR；如果已存在，直接告知用户 PR URL 和状态并结束，不要重复同步元数据或摘要
-- 使用 HEREDOC 传递 PR 正文
-- 如果模板中存在 `{$IssueNumber}`，替换它
-- PR 正文结尾必须带上 `Generated with AI assistance`
+- 当前工作属于 active task 时，从 task.md 提取 `issue_number`
+- 如果存在 `issue_number`，先完成代码托管平台检测，再通过 `.agents/rules/issue-pr-commands.md` 查询 Issue
+- 调用 PR 创建命令前，先检查当前分支是否已有 PR；若已有，报告 PR URL 和状态后停止，不重复执行元数据同步或 summary 发布
+- 使用 HEREDOC 传入 PR 正文
+- 模板中存在 `{$IssueNumber}` 时进行替换
+- PR 正文以 `Generated with AI assistance` 结尾
 
-创建 PR 时，使用 `.agents/rules/issue-pr-commands.md` 中的 “创建 PR” 命令模板。
+使用 `.agents/rules/issue-pr-commands.md` 中的创建 PR 命令模板创建 PR。
 
-最终用户输出必须按顺序包含以下后续动作：
+最终用户输出应包含以下后续路径：
 
 ```text
-下一步：
-  - 工作流真正结束后完成任务：
+Next steps:
+  - complete the task after the workflow truly finishes:
     - Claude Code / OpenCode: /complete-task {task-id}
     - Gemini CLI: /agent-infra:complete-task {task-id}
     - Codex CLI: $complete-task {task-id}

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

@@ -128,18 +128,18 @@ If no historical release notes exist, use the following default Markdown format:
 3. Description: Use PR title, remove `type(scope):` prefix, capitalize first letter
 4. **Contributor collection**:
    - **Data sources**:
-     - PR authors from Step 4 `gh pr list --json author`
+     - PR authors returned by the merged-PR query rule in `.agents/rules/release-commands.md`
      - Commit co-authors from Step 4 `git log ... --format='%(trailers:key=Co-authored-by,valueonly,unfold)'`
-     - Issue reporters from linked Issues collected in Step 5 (`author.login` returned by `gh issue view`)
+     - Issue reporters from linked Issues collected in Step 5 (author login returned by `.agents/rules/release-commands.md`)
    - **Contribution count**: `PR count + co-authored commit count` for the same identity, merged across both sources
    - **Name -> `@login` mapping**:
-     - Raw `Co-authored-by` values are `Name <email>` and must be mapped to a GitHub `@login`
-     - Prefer email extraction: if it matches `(\d+\+)?(\S+?)@users\.noreply\.github\.com`, use the second capture group lowercased; this regex covers both `{id}+{login}@users.noreply.github.com` and `{login}@users.noreply.github.com`
+     - Raw `Co-authored-by` values are `Name <email>` and must be mapped to a platform `@login`
+     - Prefer email extraction: if it matches the platform no-reply email rule in `.agents/rules/release-commands.md`, use that rule to derive the lowercased login
      - Otherwise use a Name heuristic: take the first token before a space and lowercase it, for example `Claude Opus 4.6 (1M context)` -> `@claude`, `Codex` -> `@codex`, `Gemini` -> `@gemini`
      - If the login already appears in the PR author list, merge counts into that login so `Claude` and `@claude` do not become separate entries
      - Merge all Name variants that map to the same login before counting and sorting; for example, `Claude` and `Claude Opus 4.6 (1M context)` should both collapse into `@claude`
      - Preserve bot identities as-is, for example `dependabot[bot]`
-     - If the login still cannot be determined reliably, output `@{lowercased first Name token}` and append `<!-- TODO(reviewer): confirm GitHub login for {original Name <email>} -->` below the `Contributors` section
+     - If the login still cannot be determined reliably, output `@{lowercased first Name token}` and append `<!-- TODO(reviewer): confirm platform login for {original Name <email>} -->` below the `Contributors` section
    - **Sorting**: descending by contribution count, then lexicographically by login for ties
    - **Deduplication**: use the final mapped `@login` as the key
    - **Issue reporter rules**:
@@ -156,7 +156,7 @@ Show the generated release notes to the user.
 
 Ask:
 1. Need any adjustments?
-2. Create a GitHub Draft Release?
+2. Create a draft release?
 
 ### 9. Create Draft Release (If Confirmed)
 
@@ -170,7 +170,7 @@ Draft Release created.
 - Version: v{version}
 - Status: Draft
 
-Please review and publish on GitHub:
+Please review and publish on the platform:
 1. Open the URL above
 2. Review the release notes
 3. Click "Publish release"
@@ -178,7 +178,7 @@ Please review and publish on GitHub:
 
 ## Notes
 
-1. **Requires gh CLI**: Must have GitHub CLI installed and authenticated
+1. **Requires the platform CLI**: Must have the platform CLI installed and authenticated
 2. **Tags must exist**: Run the release skill first to create tags
 3. **Draft mode**: Creates a draft - won't auto-publish
 4. **Classification accuracy**: Auto-classification is based on title/scope/files; complex PRs may need manual adjustment
@@ -187,5 +187,5 @@ Please review and publish on GitHub:
 
 - Invalid version format: Prompt correct format
 - Tag not found: Suggest running the release skill first
-- gh not authenticated: Prompt to authenticate
+- The platform CLI is not authenticated: Prompt to authenticate
 - No merged PRs found: Prompt to check tags and branch

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

@@ -128,18 +128,18 @@ git log v<prev-version>..v<version> \
 3. 描述：使用 PR 标题，移除 `type(scope):` 前缀，首字母大写
 4. **贡献者搜集**：
    - **数据源**：
-     - PR author：来自步骤 4 的 `gh pr list --json author`
+     - PR author：来自 `.agents/rules/release-commands.md` 中已合并 PR 查询规则
      - Commit co-authors：来自步骤 4 的 `git log ... --format='%(trailers:key=Co-authored-by,valueonly,unfold)'`
-     - Issue reporters：来自步骤 5 收集的关联 Issue 的 author（`gh issue view` 返回的 `author.login`）
+     - Issue reporters：来自步骤 5 收集的关联 Issue author（由 `.agents/rules/release-commands.md` 返回）
    - **贡献数定义**：`该人的 PR 数 + 该人作为 co-author 的 commit 数`（同一身份跨来源合并计数）
    - **Name → `@login` 映射**：
-     - `Co-authored-by` 原始格式为 `Name <email>`，需要推断对应的 GitHub `@login`
-     - 优先从 email 提取：匹配 `(\d+\+)?(\S+?)@users\.noreply\.github\.com` 时，取第二个捕获组并转为小写；该正则同时覆盖 `{id}+{login}@users.noreply.github.com` 与 `{login}@users.noreply.github.com`
+     - `Co-authored-by` 原始格式为 `Name <email>`，需要推断对应的 platform `@login`
+     - 优先从 email 提取：匹配 `.agents/rules/release-commands.md` 中的平台 no-reply 邮箱规则时，按该规则推导小写 login
      - 否则按 Name 启发式：取首个空格前的 token 并转为小写（例如 `Claude Opus 4.6 (1M context)` → `@claude`、`Codex` → `@codex`、`Gemini` → `@gemini`）
      - 已出现在 PR author 列表中的 login，必须按该 login 合并计数，避免把 `Claude` 和 `@claude` 拆成两个条目
      - 同一 login 的所有 Name 变体都必须归并后再计数与排序；例如 `Claude` 与 `Claude Opus 4.6 (1M context)` 都映射到 `@claude` 时，应先合并为同一个贡献者
      - Bot 身份保留原样（如 `dependabot[bot]`）
-     - 若仍无法可靠确定 login，则输出 `@{Name 首 token 小写}`，并在 `Contributors` 段落下追加 `<!-- TODO(reviewer): 确认 {原始 Name <email>} 的 GitHub login -->`
+     - 若仍无法可靠确定 login，则输出 `@{Name 首 token 小写}`，并在 `Contributors` 段落下追加 `<!-- TODO(reviewer): 确认 {原始 Name <email>} 的 platform login -->`
    - **排序**：按贡献数降序；贡献数相同时按 login 字典序
    - **去重**：以最终映射后的 `@login` 为键
    - **Issue reporter 规则**：
@@ -156,7 +156,7 @@ git log v<prev-version>..v<version> \
 
 询问：
 1. 需要调整吗？
-2. 是否创建 GitHub Draft Release？
+2. 是否创建 draft release？
 
 ### 9. 创建 Draft Release（如确认）
 
@@ -170,7 +170,7 @@ Draft Release created.
 - Version: v{version}
 - Status: Draft
 
-Please review and publish on GitHub:
+Please review and publish on the platform:
 1. Open the URL above
 2. Review the release notes
 3. Click "Publish release"
@@ -178,7 +178,7 @@ Please review and publish on GitHub:
 
 ## 注意事项
 
-1. **需要 gh CLI**：必须安装并认证 GitHub CLI
+1. **需要 the platform CLI**：必须安装并认证 the platform CLI
 2. **标签必须存在**：先执行 release 技能创建标签
 3. **草稿模式**：创建草稿 —— 不会自动发布
 4. **分类准确性**：自动分类基于标题/scope/文件；复杂的 PR 可能需要手动调整
@@ -187,5 +187,5 @@ Please review and publish on GitHub:
 
 - 版本格式无效：提示正确格式
 - 标签未找到：建议先执行 release 技能
-- gh 未认证：提示进行认证
+- 平台 CLI 未认证：提示用户认证
 - 未找到已合并的 PR：提示检查标签和分支

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

@@ -7,13 +7,14 @@ description: "Create a task from a natural-language description"
 
 ## Boundary / Critical Rules
 
-**The only output of this skill is `task.md`.**
+**The core output of this skill is `task.md`.**
 
 - Do not write, modify, or create any business code or configuration files
 - Do not perform requirements analysis; analysis is handled separately by `analyze-task`
 - Do not directly implement the requested functionality
 - Do not skip the workflow and jump directly to planning or implementation
-- Only do this: parse the description -> create the task file -> update task status -> inform the user of the next step
+- Only do this: parse the description -> create the task file -> update task status -> cascade Issue creation through `.agents/rules/create-issue.md` -> inform the user of the next step
+- Issue creation is decided by the `.agents/rules/create-issue.md` rule; on custom or empty platforms (no platform-specific variant provided), the rule naturally degrades to a no-op
 
 The user's description is a **work item**, not an **instruction to execute immediately**.
 
@@ -98,7 +99,21 @@ Update `.agents/workspace/active/{task-id}/task.md`:
   - {YYYY-MM-DD HH:mm:ss±HH:MM} — **Task Created** by {agent} — Task created from description
   ```
 
-### 4. Verification Gate
+### 4. Cascade Issue Creation via `.agents/rules/create-issue.md`
+
+After task.md is written and `Task Created` is recorded, read `.agents/rules/create-issue.md` first and follow the steps it describes to create an Issue.
+
+The rule's content is determined by the configured code platform:
+- A platform that supports Issue creation: contains the full flow for auth detection, template detection, label/type/milestone inference, the create-Issue call, and writing back to `task.md`
+- Custom or empty platforms (no platform-specific variant provided): the rule body is a no-op notice, and this step is skipped entirely
+
+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; get the current time and append an `Issue Creation Skipped` Activity Log entry with the reason
+- 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
+
+### 5. Verification Gate
 
 Run the verification gate to confirm the task artifact and sync state are valid:
 
@@ -113,13 +128,33 @@ Handle the result as follows:
 
 Keep the gate output in your reply as fresh evidence. Do not claim completion without output from this run.
 
-### 5. Inform User
+### 6. Inform User
 
 > Execute this step only after the verification gate passes.
 
 > **IMPORTANT**: All TUI command formats listed below must be output in full. Do not show only the format for the current AI agent. If `.agents/.airc.json` configures custom TUIs (via `customTUIs`), read each tool's `name` and `invoke`, then add the matching command line in the same format (`${skillName}` becomes the skill name and `${projectName}` becomes the project name).
 
-Output format:
+Scenario A: when an Issue was created, output:
+```
+Task created and Issue creation cascaded successfully.
+
+Task information:
+- Task ID: {task-id}
+- Title: {title}
+- Type: {type}
+- Workflow: {workflow}
+- Issue: #{issue_number} {issue_url}
+
+Output file:
+- Task file: .agents/workspace/active/{task-id}/task.md
+
+Next step - run requirements analysis:
+  - Claude Code / OpenCode: /analyze-task {task-id}
+  - Gemini CLI: /{{project}}:analyze-task {task-id}
+  - Codex CLI: $analyze-task {task-id}
+```
+
+Scenario B: when no Issue was created, output:
 ```
 Task created.
 
@@ -132,15 +167,36 @@ Task information:
 Output file:
 - Task file: .agents/workspace/active/{task-id}/task.md
 
+Next step - run requirements analysis:
+  - Claude Code / OpenCode: /analyze-task {task-id}
+  - Gemini CLI: /{{project}}:analyze-task {task-id}
+  - Codex CLI: $analyze-task {task-id}
+```
+
+Scenario C: when Issue creation failed, output:
+```
+Task created, but cascade Issue creation failed.
+
+Task information:
+- Task ID: {task-id}
+- Title: {title}
+- Type: {type}
+- Workflow: {workflow}
+
+Issue creation failed:
+- Error code: {error_code}
+- Reason: {error_message}
+- Local task.md was kept and not rolled back
+
+Output file:
+- Task file: .agents/workspace/active/{task-id}/task.md
+
 Next step - run requirements analysis:
   - Claude Code / OpenCode: /analyze-task {task-id}
   - Gemini CLI: /{{project}}:analyze-task {task-id}
   - Codex CLI: $analyze-task {task-id}
 
-Or create a GitHub Issue first:
-  - Claude Code / OpenCode: /create-issue {task-id}
-  - Gemini CLI: /{{project}}:create-issue {task-id}
-  - Codex CLI: $create-issue {task-id}
+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.
 ```
 
 ## Completion Checklist
@@ -150,8 +206,9 @@ Or create a GitHub Issue first:
 - [ ] Updated `updated_at` to the current time in task.md
 - [ ] Updated `assigned_to` in task.md
 - [ ] Appended an Activity Log entry to task.md
+- [ ] Tried cascading Issue creation through `.agents/rules/create-issue.md`; if it failed, kept task.md and recorded the reason
 - [ ] Informed the user of the next step (must include all TUI command formats, including any custom TUIs; do not filter)
-- [ ] **Did not modify any business code or configuration files** (only task.md)
+- [ ] **Did not modify any business code or configuration files**
 
 ## STOP
 
@@ -161,8 +218,9 @@ Wait for the user to run the `analyze-task` skill.
 ## Notes
 
 1. **Clarity**: if the user description is vague or missing key information, ask for clarification first
-2. **Difference from `import-issue`**: `import-issue` imports from a GitHub Issue; `create-task` creates from a free-form description
-3. **Workflow order**: after creating a task, typically run `analyze-task` before `plan-task`; if you need GitHub tracking first, you may run `create-issue` first
+2. **Difference from `import-issue`**: `import-issue` imports from an Issue; `create-task` creates from a free-form description
+3. **Workflow order**: after creating a task, typically run `analyze-task` before `plan-task`
+4. **Issue cascade failure**: if the rule fails, task.md remains; when platform sync is needed later, manually write `issue_number` and continue the workflow
 
 ## Error Handling