@fitlab-ai/agent-infra 0.5.1 → 0.5.2

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

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 关联

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/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

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`：告警编号

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

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`：告警编号

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).
@@ -74,13 +72,7 @@ Update `.agents/workspace/active/{task-id}/task.md`:
 
 ### 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 标题的原始语言）。
@@ -74,13 +72,7 @@ date "+%Y-%m-%d %H:%M:%S"
 
 ### 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/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`