@fitlab-ai/agent-infra 0.5.1 → 0.5.2

package/templates/.agents/rules/label-milestone-setup.github.en.md

@@ -0,0 +1,50 @@
+# Label / Milestone Platform Commands
+
+Read this file before initializing labels, initializing milestones, or adjusting milestones during release work.
+
+## Authentication and Repository Info
+
+```bash
+gh auth token
+gh repo view --json nameWithOwner --jq '.nameWithOwner'
+```
+
+## Label Operations
+
+List existing labels:
+
+```bash
+gh label list --limit 200 --json name --jq '.[].name'
+```
+
+Create or update a label:
+
+```bash
+gh label create "{name}" --color "{color}" --description "{description}" --force
+```
+
+## Milestone Operations
+
+List milestones:
+
+```bash
+gh api "repos/$repo/milestones?state=all" --paginate
+```
+
+Create a milestone:
+
+```bash
+gh api "repos/$repo/milestones" -f title="{title}" -f description="{description}" -f state="{state}"
+```
+
+Update a milestone:
+
+```bash
+gh api "repos/$repo/milestones/{number}" -X PATCH -f state="{state}" -f description="{description}"
+```
+
+## Constraints
+
+- use label names as the idempotency key
+- use milestone titles as the idempotency key, then milestone numbers when patching state
+- stop or skip according to the calling skill when commands fail

package/templates/.agents/rules/label-milestone-setup.github.zh-CN.md

@@ -0,0 +1,50 @@
+# Label / Milestone 平台命令
+
+在初始化 label、初始化 milestone，或发布流程需要调整 milestone 前先读取本文件。
+
+## 认证与仓库信息
+
+```bash
+gh auth token
+gh repo view --json nameWithOwner --jq '.nameWithOwner'
+```
+
+## Label 操作
+
+列出现有 label：
+
+```bash
+gh label list --limit 200 --json name --jq '.[].name'
+```
+
+创建或更新 label：
+
+```bash
+gh label create "{name}" --color "{color}" --description "{description}" --force
+```
+
+## Milestone 操作
+
+列出 milestone：
+
+```bash
+gh api "repos/$repo/milestones?state=all" --paginate
+```
+
+创建 milestone：
+
+```bash
+gh api "repos/$repo/milestones" -f title="{title}" -f description="{description}" -f state="{state}"
+```
+
+更新 milestone：
+
+```bash
+gh api "repos/$repo/milestones/{number}" -X PATCH -f state="{state}" -f description="{description}"
+```
+
+## 约束
+
+- label 以名称作为幂等键
+- milestone 以标题作为幂等键，必要时再结合编号更新状态
+- 失败时按调用方规则决定停止或跳过

package/templates/.agents/rules/release-commands.github.en.md

@@ -0,0 +1,30 @@
+# Release Platform Commands
+
+Read this file before loading release history, querying merged PRs, or creating a draft release.
+
+## Query Releases
+
+```bash
+gh release list --limit {limit} --json tagName,isDraft,isPrerelease
+gh release view "{tag}" --json body,url
+```
+
+## Query Merged PRs
+
+```bash
+gh pr list --state merged --base "{branch}" --json number,title,mergedAt,labels
+```
+
+When needed, read the linked Issue:
+
+```bash
+gh issue view {issue-number} --json number,title,labels,url
+```
+
+## Create a Draft Release
+
+```bash
+gh release create "v{version}" --draft --title "v{version}" --notes-file "{notes-file}"
+```
+
+If commands fail, stop or escalate according to the calling skill.

package/templates/.agents/rules/release-commands.github.zh-CN.md

@@ -0,0 +1,30 @@
+# Release 平台命令
+
+在读取历史 release、查询已合并 PR，或创建 draft release 前先读取本文件。
+
+## Release 查询
+
+```bash
+gh release list --limit {limit} --json tagName,isDraft,isPrerelease
+gh release view "{tag}" --json body,url
+```
+
+## 已合并 PR 查询
+
+```bash
+gh pr list --state merged --base "{branch}" --json number,title,mergedAt,labels
+```
+
+必要时读取关联 Issue：
+
+```bash
+gh issue view {issue-number} --json number,title,labels,url
+```
+
+## 创建 Draft Release
+
+```bash
+gh release create "v{version}" --draft --title "v{version}" --notes-file "{notes-file}"
+```
+
+失败时按调用方规则停止或提示人工介入。

package/templates/.agents/rules/security-alerts.github.en.md

@@ -0,0 +1,43 @@
+# Security Alert Platform Commands
+
+Read this file before importing or dismissing Dependabot or Code Scanning alerts.
+
+## Dependabot Alerts
+
+Read an alert:
+
+```bash
+gh api "repos/{owner}/{repo}/dependabot/alerts/{number}"
+```
+
+Dismiss an alert:
+
+```bash
+gh api --method PATCH "repos/{owner}/{repo}/dependabot/alerts/{number}" \
+  -f state="dismissed" \
+  -f dismissed_reason="{reason}" \
+  -f dismissed_comment="{comment}"
+```
+
+## Code Scanning Alerts
+
+Read an alert:
+
+```bash
+gh api "repos/{owner}/{repo}/code-scanning/alerts/{number}"
+```
+
+Dismiss an alert:
+
+```bash
+gh api --method PATCH "repos/{owner}/{repo}/code-scanning/alerts/{number}" \
+  -f state="dismissed" \
+  -f dismissed_reason="{reason}" \
+  -f dismissed_comment="{comment}"
+```
+
+## Constraints
+
+- read the current alert state before deciding whether to continue
+- validate dismissal reasons in the calling skill before sending them
+- stop or escalate according to the calling skill when API calls fail

package/templates/.agents/rules/security-alerts.github.zh-CN.md

@@ -0,0 +1,43 @@
+# 安全告警平台命令
+
+在导入或关闭 Dependabot / Code Scanning 告警前先读取本文件。
+
+## Dependabot 告警
+
+读取告警：
+
+```bash
+gh api "repos/{owner}/{repo}/dependabot/alerts/{number}"
+```
+
+关闭告警：
+
+```bash
+gh api --method PATCH "repos/{owner}/{repo}/dependabot/alerts/{number}" \
+  -f state="dismissed" \
+  -f dismissed_reason="{reason}" \
+  -f dismissed_comment="{comment}"
+```
+
+## Code Scanning 告警
+
+读取告警：
+
+```bash
+gh api "repos/{owner}/{repo}/code-scanning/alerts/{number}"
+```
+
+关闭告警：
+
+```bash
+gh api --method PATCH "repos/{owner}/{repo}/code-scanning/alerts/{number}" \
+  -f state="dismissed" \
+  -f dismissed_reason="{reason}" \
+  -f dismissed_comment="{comment}"
+```
+
+## 约束
+
+- 先读取当前告警状态，再决定是否继续
+- 关闭理由必须由调用方校验后再传入
+- API 失败时按调用方规则停止或提示人工介入

package/templates/.agents/scripts/validate-artifact.js

@@ -1,5 +1,3 @@
-#!/usr/bin/env node
-
 import fs from "node:fs";
 import path from "node:path";
 import process from "node:process";

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

@@ -9,7 +9,7 @@ description: "Cancel an unneeded task and archive it"
 
 - This command terminates a task that no longer needs to continue and archives it into `completed/`
 - Cancel only when the task no longer needs implementation, review, or follow-up work
-- When a valid `issue_number` exists, GitHub Issue sync is required
+- When a valid `issue_number` exists, Issue sync is required
 
 ## Steps
 
@@ -27,7 +27,7 @@ Handling rules:
 
 ### 2. Choose the Cancellation Label
 
-Infer the GitHub Issue closing label from the cancellation reason:
+Infer the Issue closing label from the cancellation reason:
 - `status: superseded`: reason implies duplicate, replaced, merged into, or already covered by another Issue or PR
 - `status: invalid`: reason implies invalid report, no real problem, cannot reproduce, or no issue after investigation
 - `status: declined`: reason implies not planned, deprioritized, or explicitly rejected
@@ -72,6 +72,7 @@ Confirm the task directory was moved successfully.
 Check whether `task.md` contains a valid `issue_number`. If not, skip this step.
 
 > Issue sync rules live in `.agents/rules/issue-sync.md`. Read that file before syncing.
+> Read `.agents/rules/issue-pr-commands.md` before closing the Issue.
 
 If a valid `issue_number` exists:
 - Replace all `status:` labels with the label inferred in Step 2
@@ -80,7 +81,7 @@ If a valid `issue_number` exists:
 - Remove all assignees
 - Publish a cancellation comment using the marker `<!-- sync-issue:{task-id}:cancel -->`
 - Create or update the `<!-- sync-issue:{task-id}:task -->` comment using the task-comment sync rules from `.agents/rules/issue-sync.md`
-- Close the Issue: `gh issue close {issue-number} --reason "not planned"`
+- Close the Issue by following the "Close an Issue" command in `.agents/rules/issue-pr-commands.md`, using the fixed reason `not planned`
 
 The cancellation comment must include at least:
 - the cancellation reason
@@ -112,7 +113,7 @@ Output format:
 Task {task-id} cancelled and archived.
 
 Cancellation reason: {reason}
-GitHub label: {status-label or skipped}
+Status label: {status-label or skipped}
 Archived to: .agents/workspace/completed/{task-id}/
 
 Next step - inspect the archived task:
@@ -125,7 +126,7 @@ Next step - inspect the archived task:
 
 - [ ] Recorded the cancellation reason and updated task.md
 - [ ] Moved the task directory into `.agents/workspace/completed/`
-- [ ] Completed GitHub sync when an Issue exists
+- [ ] Completed Issue sync when an Issue exists
 - [ ] Ran and passed the verification gate
 - [ ] Showed the full next-step command set to the user
 
@@ -139,4 +140,4 @@ Next step - inspect the archived task:
 
 - Task not found: `Task {task-id} not found`
 - Task already archived: inform the user it is already in `completed/`
-- Issue sync failed: keep the local archive result and tell the user manual GitHub follow-up is required
+- Issue sync failed: keep the local archive result and tell the user manual platform follow-up is required

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

@@ -9,7 +9,7 @@ description: "取消不再需要的任务并归档"
 
 - 本命令用于终止一个不再需要继续执行的任务，并归档到 `completed/`
 - 只有在确认该任务无需继续实现、审查或修复时才可取消
-- 有效 `issue_number` 存在时，GitHub Issue 同步属于必做项
+- 有效 `issue_number` 存在时，Issue 同步属于必做项
 
 ## 执行步骤
 
@@ -27,7 +27,7 @@ description: "取消不再需要的任务并归档"
 
 ### 2. 判断取消标签
 
-根据取消原因推断 GitHub Issue 关闭标签：
+根据取消原因推断 Issue 关闭标签：
 - `status: superseded`：原因包含“重复”、“替代”、“合并到”、“已由 #123 / PR 替代”等语义
 - `status: invalid`：原因包含“误报”、“不存在”、“无法复现”、“排查后无问题”等语义
 - `status: declined`：原因包含“不做”、“暂不实现”、“优先级调整”、“方案否决”等语义
@@ -72,6 +72,7 @@ ls .agents/workspace/completed/{task-id}/task.md
 检查 `task.md` 中是否存在有效的 `issue_number`。如果没有，跳过此步骤。
 
 > Issue 同步规则见 `.agents/rules/issue-sync.md`。执行同步前先读取该文件。
+> 关闭 Issue 前先读取 `.agents/rules/issue-pr-commands.md`。
 
 如果存在有效的 `issue_number`：
 - 替换所有 `status:` labels，并设置步骤 2 推断出的标签
@@ -80,7 +81,7 @@ ls .agents/workspace/completed/{task-id}/task.md
 - 移除全部 assignees
 - 发布取消评论，隐藏标记使用 `<!-- sync-issue:{task-id}:cancel -->`
 - 使用 `.agents/rules/issue-sync.md` 的 task.md 评论同步规则创建或更新 `<!-- sync-issue:{task-id}:task -->` 评论
-- 关闭 Issue：`gh issue close {issue-number} --reason "not planned"`
+- 关闭 Issue：按 `.agents/rules/issue-pr-commands.md` 中的“关闭 Issue”命令执行，关闭原因固定为 `not planned`
 
 取消评论至少包含：
 - 取消原因
@@ -112,7 +113,7 @@ node .agents/scripts/validate-artifact.js gate cancel-task .agents/workspace/com
 任务 {task-id} 已取消并归档。
 
 取消原因：{reason}
-GitHub 标签：{status-label 或 skipped}
+状态标签：{status-label 或 skipped}
 归档路径：.agents/workspace/completed/{task-id}/
 
 下一步 - 查看归档任务：
@@ -125,7 +126,7 @@ GitHub 标签：{status-label 或 skipped}
 
 - [ ] 已记录取消原因并更新 task.md
 - [ ] 已将任务目录移动到 `.agents/workspace/completed/`
-- [ ] 已在存在 Issue 时完成 GitHub 同步
+- [ ] 已在存在 Issue 时完成 Issue 同步
 - [ ] 已运行 gate 校验并通过
 - [ ] 已向用户展示完整的下一步命令
 
@@ -139,4 +140,4 @@ GitHub 标签：{status-label 或 skipped}
 
 - 任务未找到：`Task {task-id} not found`
 - 任务已归档：提示任务已在 `completed/` 中
-- Issue 同步失败：保留本地归档结果，并告知用户需要人工补齐 GitHub 操作
+- Issue 同步失败：保留本地归档结果，并告知用户需要人工补齐平台操作

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

@@ -11,9 +11,7 @@ Dismiss the specified Code Scanning (CodeQL) alert and record a justified reason
 
 ### 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.
 
 Verify that the alert is in the `open` state. If it is already dismissed or fixed, inform the user and exit.
 
@@ -61,13 +59,7 @@ Confirm? (y/N)
 
 ### 6. Execute the Dismissal
 
-```bash
-gh api --method PATCH \
-  repos/{owner}/{repo}/code-scanning/alerts/<alert-number> \
-  -f state=dismissed \
-  -f dismissed_reason="{api-reason}" \
-  -f dismissed_comment="{user explanation}"
-```
+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):
 - False Positive -> `false positive`
@@ -115,7 +107,7 @@ Next step - complete and archive the task if a related task exists:
 ## Notes
 
 1. **Handle high-severity alerts carefully**: Critical/High alerts require thorough analysis. Prefer `import-codescan` + `analyze-task` first.
-2. **Use truthful reasons**: dismissal records are stored in GitHub and may be audited.
+2. **Use truthful reasons**: dismissal records are stored on the platform and may be audited.
 3. **Review periodically**: dismissed alerts should be re-evaluated over time.
 4. **Fix first**: dismissal should be the last resort.
 

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

@@ -11,9 +11,7 @@ description: "关闭 Code Scanning 告警并记录理由"
 
 ### 1. 获取告警信息
 
-```bash
-gh api repos/{owner}/{repo}/code-scanning/alerts/<alert-number>
-```
+执行前先读取 `.agents/rules/security-alerts.md`，并按其中的 Code Scanning 告警读取命令获取告警详情。
 
 验证告警处于 `open` 状态。如果已被关闭/修复，告知用户并退出。
 
@@ -61,13 +59,7 @@ Code Scanning 告警 #{alert-number}
 
 ### 6. 执行关闭
 
-```bash
-gh api --method PATCH \
-  repos/{owner}/{repo}/code-scanning/alerts/<alert-number> \
-  -f state=dismissed \
-  -f dismissed_reason="{api-reason}" \
-  -f dismissed_comment="{用户的说明}"
-```
+按 `.agents/rules/security-alerts.md` 中的 Code Scanning 告警关闭命令执行关闭操作，并传入映射后的 `{api-reason}` 与用户说明。
 
 **API reason 映射**（按 GitHub Code Scanning API）：
 - 误报 -> `false positive`
@@ -115,7 +107,7 @@ Code Scanning 告警 #{alert-number} 已关闭。
 ## 注意事项
 
 1. **谨慎处理高严重程度告警**：Critical/High 告警需要充分分析。建议先执行 import-codescan + analyze-task。
-2. **真实的理由**：关闭记录保存在 GitHub 中，可能会被审计。
+2. **真实的理由**：关闭记录保存在平台中，可能会被审计。
 3. **定期复查**：已关闭的告警应定期复查。
 4. **优先修复**：关闭应作为最后手段。
 

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

@@ -11,9 +11,7 @@ Dismiss the specified Dependabot security alert and record a justified reason.
 
 ### 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.
 
 Verify that the alert is in the `open` state. If it is already dismissed or fixed, inform the user and exit.
 
@@ -67,13 +65,7 @@ Confirm? (y/N)
 
 ### 6. Execute the Dismissal
 
-```bash
-gh api --method PATCH \
-  repos/{owner}/{repo}/dependabot/alerts/<alert-number> \
-  -f state=dismissed \
-  -f dismissed_reason="{api-reason}" \
-  -f dismissed_comment="{user explanation}"
-```
+Dismiss the alert by following the Dependabot dismiss command in `.agents/rules/security-alerts.md`, passing the mapped `{api-reason}` and the user's explanation.
 
 **API reason mapping**:
 - False Positive -> `not_used` or `inaccurate`
@@ -110,9 +102,9 @@ Severity: {severity}
 Reason: {reason}
 Explanation: {explanation}
 
-View: https://github.com/{owner}/{repo}/security/dependabot/{alert-number}
+View: {alert-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}
@@ -123,7 +115,7 @@ Next step - complete and archive the task if a related task exists:
 ## Notes
 
 1. **Handle high-severity alerts carefully**: Critical/High alerts require thorough analysis before dismissal. Prefer `import-dependabot` + `analyze-task` first.
-2. **Use truthful reasons**: dismissal records are stored in GitHub and may be audited.
+2. **Use truthful reasons**: dismissal records are stored on the platform and may be audited.
 3. **Review periodically**: dismissed alerts should be re-evaluated because code changes may invalidate the dismissal rationale.
 4. **Fix first**: dismissal should be the last resort. Prefer upgrading, replacing, or mitigating.
 

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

@@ -11,9 +11,7 @@ description: "关闭 Dependabot 安全告警并记录理由"
 
 ### 1. 获取告警信息
 
-```bash
-gh api repos/{owner}/{repo}/dependabot/alerts/<alert-number>
-```
+执行前先读取 `.agents/rules/security-alerts.md`，并按其中的 Dependabot 告警读取命令获取告警详情。
 
 验证告警处于 `open` 状态。如果已被关闭/修复，告知用户并退出。
 
@@ -67,13 +65,7 @@ CVE：{cve-id}
 
 ### 6. 执行关闭
 
-```bash
-gh api --method PATCH \
-  repos/{owner}/{repo}/dependabot/alerts/<alert-number> \
-  -f state=dismissed \
-  -f dismissed_reason="{api-reason}" \
-  -f dismissed_comment="{用户的说明}"
-```
+按 `.agents/rules/security-alerts.md` 中的 Dependabot 告警关闭命令执行关闭操作，并传入映射后的 `{api-reason}` 与用户说明。
 
 **API reason 映射**：
 - 误报 -> `not_used` 或 `inaccurate`
@@ -110,9 +102,9 @@ date "+%Y-%m-%d %H:%M:%S"
 原因：{reason}
 说明：{explanation}
 
-查看：https://github.com/{owner}/{repo}/security/dependabot/{alert-number}
+查看：{alert-url}
 
-注意：如有需要，可在 GitHub 上重新打开。
+注意：如有需要，可在平台侧重新打开。
 
 下一步 - 完成并归档任务（如有关联任务）：
   - Claude Code / OpenCode：/complete-task {task-id}
@@ -123,7 +115,7 @@ date "+%Y-%m-%d %H:%M:%S"
 ## 注意事项
 
 1. **谨慎处理高严重程度告警**：Critical/High 告警需要在关闭前进行充分分析。建议先执行 import-dependabot + analyze-task。
-2. **真实的理由**：关闭记录保存在 GitHub 中，可能会被审计。
+2. **真实的理由**：关闭记录保存在平台中，可能会被审计。
 3. **定期复查**：已关闭的告警应定期复查，因为代码变更可能使关闭理由失效。
 4. **优先修复**：关闭应作为最后手段。优先考虑升级、替换或缓解。
 

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,10 +39,7 @@ 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
 

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,10 +39,7 @@ 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. 更新任务状态
 

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`）→ 添加