@fitlab-ai/agent-infra 0.3.0

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

@@ -0,0 +1,119 @@
+---
+name: import-issue
+description: >
+  从 GitHub Issue 导入并创建任务文件。
+  当用户要求导入某个 Issue 时触发。参数：issue 编号。
+---
+
+# 导入 Issue
+
+导入指定的 GitHub Issue 并创建任务。参数：issue 编号。
+
+## 行为边界 / 关键规则
+
+- 本技能的唯一产出是 `task.md`
+- 不要编写或修改业务代码。仅做导入
+- 执行本技能后，你**必须**立即更新任务状态
+
+## 执行流程
+
+### 1. 获取 Issue 信息
+
+```bash
+gh issue view <issue-number> --json number,title,body,labels
+```
+
+提取：issue 编号、标题、描述、标签。
+
+### 2. 检查已有任务
+
+搜索 `.agent-workspace/active/` 中是否已有链接到此 Issue 的任务。
+- 如果找到，询问用户是重新导入还是继续使用现有任务
+- 如果未找到，创建新任务
+
+### 3. 创建任务目录和文件
+
+```bash
+date +%Y%m%d-%H%M%S
+```
+
+- 创建目录：`.agent-workspace/active/TASK-{yyyyMMdd-HHmmss}/`
+- 使用 `.agents/templates/task.md` 模板创建 `task.md`
+
+任务元数据：
+```yaml
+id: TASK-{yyyyMMdd-HHmmss}
+issue_number: <issue-number>
+type: feature|bugfix|refactor|docs|chore
+workflow: feature-development|bug-fix|refactoring
+status: active
+created_at: {yyyy-MM-dd HH:mm:ss}
+updated_at: {yyyy-MM-dd HH:mm:ss}
+created_by: human
+current_step: requirement-analysis
+assigned_to: {当前 AI 代理}
+```
+
+### 4. 更新任务状态
+
+获取当前时间：
+
+```bash
+date "+%Y-%m-%d %H:%M:%S"
+```
+
+更新 `.agent-workspace/active/{task-id}/task.md`：
+- `current_step`：requirement-analysis
+- `assigned_to`：{当前 AI 代理}
+- `updated_at`：{当前时间}
+- **追加**到 `## Activity Log`（不要覆盖之前的记录）：
+  ```
+  - {yyyy-MM-dd HH:mm:ss} — **Import Issue** by {agent} — Issue #{number} imported
+  ```
+
+### 5. 告知用户
+
+> **重要**：以下「下一步」中列出的所有 TUI 命令格式必须完整输出，不要只展示当前 AI 代理对应的格式。
+
+```
+Issue #{number} 已导入。
+
+任务信息：
+- 任务 ID：{task-id}
+- 标题：{title}
+- 工作流：{workflow}
+
+产出文件：
+- 任务文件：.agent-workspace/active/{task-id}/task.md
+
+下一步 - 执行需求分析：
+  - Claude Code / OpenCode：/analyze-task {task-id}
+  - Gemini CLI：/agent-infra:analyze-task {task-id}
+  - Codex CLI：$analyze-task {task-id}
+```
+
+## 完成检查清单
+
+- [ ] 创建了任务文件 `.agent-workspace/active/{task-id}/task.md`
+- [ ] 在 task.md 中记录了 issue_number
+- [ ] 更新了 `current_step` 为 requirement-analysis
+- [ ] 更新了 `updated_at` 为当前时间
+- [ ] 追加了 Activity Log 条目到 task.md
+- [ ] 告知了用户下一步（必须展示所有 TUI 的命令格式，不要筛选）
+- [ ] **没有修改任何业务代码**
+
+## 停止
+
+完成检查清单后，**立即停止**。不要继续执行后续步骤。
+
+## 注意事项
+
+1. **Issue 验证**：在继续之前检查 Issue 是否存在
+2. **重复任务**：如果此 Issue 已有关联任务，在创建新任务前询问用户
+3. **下一步**：导入完成后，先执行 `analyze-task`，再进入 `plan-task`
+
+## 错误处理
+
+- Issue 未找到：提示 "Issue #{number} not found, please check the issue number"
+- 网络错误：提示 "Cannot connect to GitHub, please check network"
+- 权限错误：提示 "No access to this repository"

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

@@ -0,0 +1,119 @@
+---
+name: import-issue
+description: >
+  从 GitHub Issue 导入并创建任务文件。
+  当用户要求导入某个 Issue 时触发。参数：issue 编号。
+---
+
+# 导入 Issue
+
+导入指定的 GitHub Issue 并创建任务。参数：issue 编号。
+
+## 行为边界 / 关键规则
+
+- 本技能的唯一产出是 `task.md`
+- 不要编写或修改业务代码。仅做导入
+- 执行本技能后，你**必须**立即更新任务状态
+
+## 执行流程
+
+### 1. 获取 Issue 信息
+
+```bash
+gh issue view <issue-number> --json number,title,body,labels
+```
+
+提取：issue 编号、标题、描述、标签。
+
+### 2. 检查已有任务
+
+搜索 `.agent-workspace/active/` 中是否已有链接到此 Issue 的任务。
+- 如果找到，询问用户是重新导入还是继续使用现有任务
+- 如果未找到，创建新任务
+
+### 3. 创建任务目录和文件
+
+```bash
+date +%Y%m%d-%H%M%S
+```
+
+- 创建目录：`.agent-workspace/active/TASK-{yyyyMMdd-HHmmss}/`
+- 使用 `.agents/templates/task.md` 模板创建 `task.md`
+
+任务元数据：
+```yaml
+id: TASK-{yyyyMMdd-HHmmss}
+issue_number: <issue-number>
+type: feature|bugfix|refactor|docs|chore
+workflow: feature-development|bug-fix|refactoring
+status: active
+created_at: {yyyy-MM-dd HH:mm:ss}
+updated_at: {yyyy-MM-dd HH:mm:ss}
+created_by: human
+current_step: requirement-analysis
+assigned_to: {当前 AI 代理}
+```
+
+### 4. 更新任务状态
+
+获取当前时间：
+
+```bash
+date "+%Y-%m-%d %H:%M:%S"
+```
+
+更新 `.agent-workspace/active/{task-id}/task.md`：
+- `current_step`：requirement-analysis
+- `assigned_to`：{当前 AI 代理}
+- `updated_at`：{当前时间}
+- **追加**到 `## Activity Log`（不要覆盖之前的记录）：
+  ```
+  - {yyyy-MM-dd HH:mm:ss} — **Import Issue** by {agent} — Issue #{number} imported
+  ```
+
+### 5. 告知用户
+
+> **重要**：以下「下一步」中列出的所有 TUI 命令格式必须完整输出，不要只展示当前 AI 代理对应的格式。
+
+```
+Issue #{number} 已导入。
+
+任务信息：
+- 任务 ID：{task-id}
+- 标题：{title}
+- 工作流：{workflow}
+
+产出文件：
+- 任务文件：.agent-workspace/active/{task-id}/task.md
+
+下一步 - 执行需求分析：
+  - Claude Code / OpenCode：/analyze-task {task-id}
+  - Gemini CLI：/agent-infra:analyze-task {task-id}
+  - Codex CLI：$analyze-task {task-id}
+```
+
+## 完成检查清单
+
+- [ ] 创建了任务文件 `.agent-workspace/active/{task-id}/task.md`
+- [ ] 在 task.md 中记录了 issue_number
+- [ ] 更新了 `current_step` 为 requirement-analysis
+- [ ] 更新了 `updated_at` 为当前时间
+- [ ] 追加了 Activity Log 条目到 task.md
+- [ ] 告知了用户下一步（必须展示所有 TUI 的命令格式，不要筛选）
+- [ ] **没有修改任何业务代码**
+
+## 停止
+
+完成检查清单后，**立即停止**。不要继续执行后续步骤。
+
+## 注意事项
+
+1. **Issue 验证**：在继续之前检查 Issue 是否存在
+2. **重复任务**：如果此 Issue 已有关联任务，在创建新任务前询问用户
+3. **下一步**：导入完成后，先执行 `analyze-task`，再进入 `plan-task`
+
+## 错误处理
+
+- Issue 未找到：提示 "Issue #{number} not found, please check the issue number"
+- 网络错误：提示 "Cannot connect to GitHub, please check network"
+- 权限错误：提示 "No access to this repository"

package/templates/.agents/skills/init-labels/SKILL.md

@@ -0,0 +1,74 @@
+---
+name: init-labels
+description: >
+  Initialize the repository's standard GitHub Labels taxonomy in one pass.
+  Create the common labels, auto-detect `in:` labels from the project structure,
+  do not create `theme:` labels, overwrite exact-match GitHub defaults, and report unmatched defaults.
+---
+
+# Initialize GitHub Labels
+
+Initialize the repository's standard GitHub Labels taxonomy.
+
+## Execution Flow
+
+### 1. Verify prerequisites
+
+Confirm that:
+- `gh` is installed
+- `gh auth token` succeeds
+- `gh repo view --json nameWithOwner` can access the current repository
+
+If any prerequisite fails, stop and report the matching error.
+
+### 2. Run the bootstrap script
+
+Execute the complete label initialization flow with:
+
+```bash
+bash .agents/skills/init-labels/scripts/init-labels.sh
+```
+
+The script is responsible for:
+- Capturing the current label snapshot before making changes
+- Creating or updating the standard label set with `gh label create --force`
+- Auto-detecting top-level directories and creating one `in:` label per valid directory
+- Falling back to `in: core` when no eligible directory is detected
+- Reporting unmatched GitHub default labels such as `question` and `wontfix`
+- Printing the final execution summary
+
+### 3. Standard taxonomy
+
+The script manages these common label families:
+- `type:` labels such as `type: bug`, `type: enhancement`, `type: feature`, `type: documentation`, `type: dependency-upgrade`, and `type: task`
+- `status:` labels such as `status: waiting-for-triage`, `status: in-progress`, and `status: waiting-for-internal-feedback`
+- GitHub-default-name labels intentionally overwritten in place: `good first issue` and `help wanted`
+- Additional shared labels such as `dependencies`
+
+### 4. Scope discovery rules
+
+Directory-derived labels follow these rules:
+- Detect top-level project directories only
+- Skip hidden directories and common generated folders
+- Create `in: core` only when no valid directory remains
+- Do not create any `theme:` labels in this skill
+
+### 5. Output and behavior guarantees
+
+The summary must include:
+- Number of common labels created or updated
+- Number of `in:` labels created or updated
+- Confirmation that exact-match GitHub defaults were overwritten
+- Any unmatched GitHub default labels still present
+
+Operational notes:
+- The operation is idempotent because every label uses `gh label create --force`.
+- If the detected `in:` labels need refinement, adjust them manually after initialization.
+
+## Error Handling
+
+- `gh` not found: prompt "GitHub CLI (`gh`) is not installed"
+- Authentication failed: prompt "GitHub CLI is not authenticated"
+- Repository access failed: prompt "Unable to access the current repository with gh"
+- Permission error: prompt "No permission to manage labels in this repository"
+- API rate limit: prompt "GitHub API rate limit reached, please retry later"

package/templates/.agents/skills/init-labels/SKILL.zh-CN.md

@@ -0,0 +1,74 @@
+---
+name: init-labels
+description: >
+  一次性初始化仓库的标准 GitHub Labels 体系。
+  创建通用 labels、基于项目目录结构自动探测 `in:` labels、
+  不创建 `theme:` labels、覆盖名称完全匹配的 GitHub 默认 labels，并提示未覆盖的默认 labels。
+---
+
+# 初始化 GitHub Labels
+
+一次性初始化仓库的标准 GitHub Labels 体系。
+
+## 执行流程
+
+### 1. 验证前置条件
+
+确认以下条件成立：
+- 已安装 `gh`
+- `gh auth token` 执行成功
+- `gh repo view --json nameWithOwner` 可以访问当前仓库
+
+如果任一条件失败，停止并输出对应错误。
+
+### 2. 运行初始化脚本
+
+执行以下命令，完成整套 label 初始化流程：
+
+```bash
+bash .agents/skills/init-labels/scripts/init-labels.sh
+```
+
+脚本负责：
+- 在修改前保存当前 label 快照
+- 使用 `gh label create --force` 创建或更新标准 label 集合
+- 自动探测顶层目录，并为有效目录创建对应的 `in:` label
+- 在没有可用目录时回退到 `in: core`
+- 提示仍然存在的 GitHub 默认 labels，例如 `question` 和 `wontfix`
+- 输出最终执行摘要
+
+### 3. 标准分类体系
+
+脚本管理以下通用 label 族：
+- `type:` labels，例如 `type: bug`、`type: enhancement`、`type: feature`、`type: documentation`、`type: dependency-upgrade`、`type: task`
+- `status:` labels，例如 `status: waiting-for-triage`、`status: in-progress`、`status: waiting-for-internal-feedback`
+- 明确覆盖的 GitHub 默认同名 labels：`good first issue` 和 `help wanted`
+- 额外通用 labels，例如 `dependencies`
+
+### 4. 范围探测规则
+
+目录派生 label 遵循以下规则：
+- 只探测项目顶层目录
+- 排除隐藏目录和常见构建/缓存目录
+- 仅当没有有效目录时才创建 `in: core`
+- 本技能不创建任何 `theme:` labels
+
+### 5. 输出与行为保证
+
+摘要必须包含：
+- 创建或更新的通用 labels 数量
+- 创建或更新的 `in:` labels 数量
+- 名称完全匹配的 GitHub 默认 labels 已被覆盖的说明
+- 仍然存在的未匹配 GitHub 默认 labels
+
+执行说明：
+- 整个操作具备幂等性，因为每个 label 都使用 `gh label create --force`。
+- 如果自动探测出的 `in:` labels 需要细化，请在初始化后手动调整。
+
+## 错误处理
+
+- 未找到 `gh`：提示 "GitHub CLI (`gh`) is not installed"
+- 认证失败：提示 "GitHub CLI is not authenticated"
+- 仓库访问失败：提示 "Unable to access the current repository with gh"
+- 权限不足：提示 "No permission to manage labels in this repository"
+- API 限流：提示 "GitHub API rate limit reached, please retry later"

package/templates/.agents/skills/init-labels/scripts/init-labels.sh

@@ -0,0 +1,111 @@
+#!/bin/sh
+
+set -e
+
+if ! command -v gh >/dev/null 2>&1; then
+  echo "GitHub CLI (\`gh\`) is not installed"
+  exit 1
+fi
+
+if ! gh auth token >/dev/null 2>&1; then
+  echo "GitHub CLI is not authenticated"
+  exit 1
+fi
+
+if ! gh repo view --json nameWithOwner >/dev/null 2>&1; then
+  echo "Unable to access the current repository with gh"
+  exit 1
+fi
+
+tmpdir="$(mktemp -d)"
+trap 'rm -rf "$tmpdir"' EXIT HUP INT TERM
+
+gh label list --limit 200 --json name --jq '.[].name' > "$tmpdir/existing-names.txt"
+cp "$tmpdir/existing-names.txt" "$tmpdir/existing.txt"
+echo "Existing labels:"
+cat "$tmpdir/existing-names.txt"
+
+cat <<'EOF' > "$tmpdir/common.tsv"
+type: bug	DED6F9	A general bug
+type: enhancement	DED6F9	A general enhancement
+type: feature	DED6F9	A general feature
+type: documentation	DED6F9	A documentation task
+type: dependency-upgrade	DED6F9	A dependency upgrade
+type: task	DED6F9	A general task
+status: waiting-for-triage	FCF1C4	An issue we've not yet triaged or decided on
+status: waiting-for-feedback	FCF1C4	We need additional information before we can continue
+status: feedback-provided	FCF1C4	Feedback has been provided
+status: feedback-reminder	FCF1C4	We've sent a reminder that we need additional information before we can continue
+status: pending-design-work	FCF1C4	Needs design work before any code can be developed
+status: in-progress	FCF1C4	Work is actively being developed
+status: on-hold	FCF1C4	We can't start working on this issue yet
+status: blocked	FCF1C4	An issue that's blocked on an external project change
+status: declined	FCF1C4	A suggestion or change that we don't feel we should currently apply
+status: duplicate	FCF1C4	A duplicate of another issue
+status: invalid	FCF1C4	An issue that we don't feel is valid
+status: superseded	FCF1C4	An issue that has been superseded by another
+status: bulk-closed	FCF1C4	An outdated, unresolved issue that's closed in bulk as part of a cleaning process
+status: ideal-for-contribution	FCF1C4	An issue that a contributor can help us with
+status: backported	FCF1C4	An issue that has been backported to maintenance branches
+status: waiting-for-internal-feedback	FCF1C4	An issue that needs input from a member or another team
+good first issue	F9D9E6	Good for newcomers
+help wanted	008672	Extra attention is needed
+dependencies	0366d6	Pull requests that update a dependency file
+EOF
+
+while IFS="$(printf '\t')" read -r name color description; do
+  [ -n "$name" ] || continue
+  gh label create "$name" --color "$color" --description "$description" --force
+done < "$tmpdir/common.tsv"
+
+project_dirs=$(
+  find . -mindepth 1 -maxdepth 1 -type d ! -name '.*' |
+  sed 's#^\./##' |
+  grep -Ev '^(node_modules|vendor|dist|build|out|target|tmp|temp|log|logs|coverage|__pycache__)$' |
+  sort -u
+)
+
+if [ -z "$project_dirs" ]; then
+  project_dirs="core"
+fi
+
+printf '%s\n' "$project_dirs" | while IFS= read -r dir; do
+  [ -n "$dir" ] || continue
+  gh label create "in: $dir" \
+    --color EBF8DF \
+    --description "Issues in $dir" \
+    --force
+done
+
+gh label list --limit 200 --json name --jq '.[].name' > "$tmpdir/final-names.txt"
+cp "$tmpdir/final-names.txt" "$tmpdir/final.txt"
+
+: > "$tmpdir/unmatched-defaults.txt"
+for label in bug documentation duplicate enhancement invalid question wontfix; do
+  if grep -Fqx "$label" "$tmpdir/final-names.txt"; then
+    printf '%s\n' "$label" >> "$tmpdir/unmatched-defaults.txt"
+  fi
+done
+
+common_count="$(wc -l < "$tmpdir/common.tsv" | tr -d ' ')"
+in_count="$(printf '%s\n' "$project_dirs" | sed '/^$/d' | wc -l | tr -d ' ')"
+
+echo "GitHub Labels initialized."
+echo
+echo "Summary:"
+echo "- Common labels created or updated: $common_count"
+echo "- in: labels created or updated: $in_count"
+echo "- Exact-match GitHub defaults overwritten: good first issue, help wanted"
+
+if [ -s "$tmpdir/unmatched-defaults.txt" ]; then
+  echo "- Unmatched GitHub defaults still present:"
+  sed 's/^/  - /' "$tmpdir/unmatched-defaults.txt"
+else
+  echo "- Unmatched GitHub defaults still present: none"
+fi
+
+echo
+echo "Notes:"
+echo "- theme: labels were intentionally not created."
+echo "- The operation is idempotent because every label uses gh label create --force."
+echo "- If the detected in: labels need refinement, adjust them manually after initialization."

package/templates/.agents/skills/init-milestones/SKILL.md

@@ -0,0 +1,74 @@
+---
+name: init-milestones
+description: >
+  Initialize the repository's standard GitHub Milestones taxonomy in one pass.
+  Create General Backlog, the initial milestones derived from the current version baseline, and optionally backfill historical milestones.
+---
+
+# Initialize GitHub Milestones
+
+Initialize the repository's standard GitHub Milestones taxonomy.
+
+## Execution Flow
+
+### 1. Verify prerequisites
+
+Confirm that:
+- `gh` is installed
+- `gh auth token` succeeds
+- `gh repo view --json nameWithOwner` can access the current repository
+
+If any prerequisite fails, stop and report the matching error.
+
+### 2. Run the bootstrap script
+
+Execute the complete milestone initialization flow with:
+
+```bash
+bash .agents/skills/init-milestones/scripts/init-milestones.sh "$ARGUMENTS"
+```
+
+The script is 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"`
+- Building the desired milestone set and creating only the missing titles
+- Printing the final execution summary
+
+### 3. Standard milestone definitions
+
+Create the following milestones with fixed descriptions:
+- `General Backlog`: `All unsorted backlogged tasks may be completed in a future version.` (state=`open`)
+- `{major}.{minor}.x`: `Issues that we want to resolve in {major}.{minor} line.` (state=`open`)
+- `{major}.{minor}.{patch+1}`: `Issues that we want to release in v{major}.{minor}.{patch+1}.` (state=`open`)
+
+When `--history` is present, each historical `vX.Y.Z` tag additionally contributes:
+- `X.Y.x` as an open line milestone
+- `X.Y.Z` as a closed release milestone (`state=closed`)
+
+### 4. Output and behavior guarantees
+
+The summary must include:
+- Version baseline
+- Whether `--history` was enabled
+- Created and skipped milestone counts
+- Newly created milestone titles
+- Already present milestone titles
+
+Operational notes:
+- Milestone titles are treated as the idempotency key.
+- 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.
+
+## Error Handling
+
+- `gh` not found: prompt "GitHub CLI (`gh`) is not installed"
+- Authentication failed: prompt "GitHub CLI is not authenticated"
+- Repository access failed: prompt "Unable to access the current repository with gh"
+- Version detection failed: prompt "Unable to determine current version baseline"
+- No `v*` tags found in `--history` mode: prompt "No history tags found matching v*; only standard milestones will be created"
+- Permission error: prompt "No permission to manage milestones in this repository"
+- API rate limit: prompt "GitHub API rate limit reached, please retry later"

package/templates/.agents/skills/init-milestones/SKILL.zh-CN.md

@@ -0,0 +1,74 @@
+---
+name: init-milestones
+description: >
+  一次性初始化仓库的标准 GitHub Milestones 体系。
+  创建 General Backlog、基于当前版本的初始里程碑，并可选补齐历史版本里程碑。
+---
+
+# 初始化 GitHub Milestones
+
+一次性初始化仓库的标准 GitHub Milestones 体系。
+
+## 执行流程
+
+### 1. 验证前置条件
+
+确认以下条件成立：
+- 已安装 `gh`
+- `gh auth token` 执行成功
+- `gh repo view --json nameWithOwner` 可以访问当前仓库
+
+如果任一条件失败，停止并输出对应错误。
+
+### 2. 运行初始化脚本
+
+执行以下命令，完成整套里程碑初始化流程：
+
+```bash
+bash .agents/skills/init-milestones/scripts/init-milestones.sh "$ARGUMENTS"
+```
+
+脚本负责：
+- 创建并清理临时工作目录
+- 检测是否传入 `--history`
+- 按“最新 `v*` Git tag → `package.json` → 默认 `0.1.0`”解析版本基线
+- 使用 `gh api "repos/$repo/milestones"` 读取当前里程碑
+- 构建目标里程碑集合，并且只创建缺失标题
+- 输出最终执行摘要
+
+### 3. 标准里程碑定义
+
+按固定描述创建以下里程碑：
+- `General Backlog`：`All unsorted backlogged tasks may be completed in a future version.`（state=`open`）
+- `{major}.{minor}.x`：`Issues that we want to resolve in {major}.{minor} line.`（state=`open`）
+- `{major}.{minor}.{patch+1}`：`Issues that we want to release in v{major}.{minor}.{patch+1}.`（state=`open`）
+
+当传入 `--history` 时，每个历史 `vX.Y.Z` tag 还会额外贡献：
+- `X.Y.x` 作为开启状态的线里程碑
+- `X.Y.Z` 作为关闭状态的版本里程碑（`state=closed`）
+
+### 4. 输出与行为保证
+
+摘要必须包含：
+- 版本基线
+- 是否启用 `--history`
+- 创建与跳过的里程碑数量
+- 新创建的里程碑标题
+- 已存在的里程碑标题
+
+执行说明：
+- Milestone titles are treated as the idempotency key.
+- General Backlog 是未分类工作的兜底里程碑。
+- 不带 `--history` 时，只为下一次 patch 发布创建版本里程碑。
+- 历史 `X.Y.Z` tag 会生成开启状态的 `X.Y.x` 和关闭状态的 `X.Y.Z`。
+- 标签较多的仓库可能触发 GitHub API rate limit。
+
+## 错误处理
+
+- 未找到 `gh`：提示 "GitHub CLI (`gh`) is not installed"
+- 认证失败：提示 "GitHub CLI is not authenticated"
+- 仓库访问失败：提示 "Unable to access the current repository with gh"
+- 版本解析失败：提示 "Unable to determine current version baseline"
+- `--history` 模式下未找到任何 `v*` git tags：提示 "No history tags found matching v*; only standard milestones will be created"
+- 权限不足：提示 "No permission to manage milestones in this repository"
+- API 限流：提示 "GitHub API rate limit reached, please retry later"