@fitlab-ai/agent-infra 0.3.1 → 0.3.2

package/README.md

@@ -114,21 +114,26 @@ These are not thin command aliases. Each skill encapsulates standardized process
 
 ```bash
 npm install -g @fitlab-ai/agent-infra
-npx @fitlab-ai/agent-infra init
 ```
 
 **Option B - Shell script**
 
 ```bash
+# Convenience wrapper — detects Node.js and runs npm install -g internally
 curl -fsSL https://raw.githubusercontent.com/fitlab-ai/agent-infra/main/install.sh | sh
 ```
 
-**Option C - Install from source**
+### Updating agent-infra
 
 ```bash
-git clone https://github.com/fitlab-ai/agent-infra.git
-cd agent-infra
-sh install.sh
+npm update -g @fitlab-ai/agent-infra
+```
+
+Check your current version:
+
+```bash
+ai version
+# or: agent-infra version
 ```
 
 ### 2. Initialize a new project
@@ -164,7 +169,7 @@ agent-infra is intentionally simple: a bootstrap CLI creates the seed configurat
 
 ### End-to-End Flow
 
-1. **Install** — `npm install -g @fitlab-ai/agent-infra` (or use the shell script)
+1. **Install** — `npm install -g @fitlab-ai/agent-infra` (or use the shell script wrapper)
 2. **Initialize** — `ai init` in the project root to generate `.airc.json` and install the seed command
 3. **Render** — run `update-agent-infra` in any AI TUI to pull templates and generate all managed files
 4. **Develop** — use 28 built-in skills to drive the full lifecycle: `analysis → design → implementation → review → fix → commit`
@@ -380,7 +385,7 @@ The generated `.airc.json` file is the central contract between the bootstrap CL
   "org": "my-org",
   "language": "en",
   "templateSource": "templates/",
-  "templateVersion": "v0.3.1",
+  "templateVersion": "v0.3.2",
   "modules": ["ai", "github"],
   "files": {
     "managed": [

package/README.zh-CN.md

@@ -114,21 +114,26 @@ agent-infra 的目标就是把这层协作面标准化。它为所有支持的 A
 
 ```bash
 npm install -g @fitlab-ai/agent-infra
-npx @fitlab-ai/agent-infra init
 ```
 
 **方式 B - Shell 脚本**
 
 ```bash
+# 便捷封装：检测 Node.js 后，内部执行 npm install -g
 curl -fsSL https://raw.githubusercontent.com/fitlab-ai/agent-infra/main/install.sh | sh
 ```
 
-**方式 C - 从源码安装**
+### 更新 agent-infra
 
 ```bash
-git clone https://github.com/fitlab-ai/agent-infra.git
-cd agent-infra
-sh install.sh
+npm update -g @fitlab-ai/agent-infra
+```
+
+查看当前版本：
+
+```bash
+ai version
+# 或：agent-infra version
 ```
 
 ### 2. 初始化新项目
@@ -164,7 +169,7 @@ agent-infra 的结构刻意保持简单：引导 CLI 负责生成种子配置，
 
 ### 端到端流程
 
-1. **安装** — `npm install -g @fitlab-ai/agent-infra`（或使用 shell 脚本）
+1. **安装** — `npm install -g @fitlab-ai/agent-infra`（或使用 shell 脚本便捷封装）
 2. **初始化** — 在项目根目录运行 `ai init`，生成 `.airc.json` 并安装种子命令
 3. **渲染** — 在任意 AI TUI 中执行 `update-agent-infra`，拉取模板并生成所有受管理文件
 4. **开发** — 使用 28 个内置 skill 驱动完整生命周期：`analysis → design → implementation → review → fix → commit`
@@ -380,7 +385,7 @@ import-issue #42                    从 GitHub Issue 导入任务
   "org": "my-org",
   "language": "en",
   "templateSource": "templates/",
-  "templateVersion": "v0.3.1",
+  "templateVersion": "v0.3.2",
   "modules": ["ai", "github"],
   "files": {
     "managed": [

package/bin/cli.js

@@ -23,7 +23,7 @@ Shorthand: ai (e.g. ai init)
 Install methods:
   npm:   npm install -g @fitlab-ai/agent-infra
   npx:   npx @fitlab-ai/agent-infra init
-  curl:  curl -fsSL https://raw.githubusercontent.com/fitlab-ai/agent-infra/main/install.sh | sh
+  curl:  curl -fsSL https://raw.githubusercontent.com/fitlab-ai/agent-infra/main/install.sh | sh  (runs npm install -g internally)
 
 Examples:
   cd my-project && agent-infra init

package/lib/version.js

@@ -1,7 +1,8 @@
 import { readFileSync } from 'node:fs';
 
-const { version: VERSION } = JSON.parse(
+const { version } = JSON.parse(
   readFileSync(new URL('../package.json', import.meta.url), 'utf8')
 );
+const VERSION = `v${version}`;
 
 export { VERSION };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@fitlab-ai/agent-infra",
-  "version": "0.3.1",
+  "version": "0.3.2",
   "description": "Bootstrap tool for AI multi-tool collaboration infrastructure — works with Claude Code, Codex, Gemini CLI, and OpenCode",
   "license": "MIT",
   "type": "module",

package/templates/.agents/README.md

@@ -100,6 +100,18 @@ Each AI tool has different strengths. Use them accordingly:
 4. **Run the workflow**: Follow the appropriate workflow in `.agents/workflows/`.
 5. **Hand off**: When switching AIs, create a handoff document from the template.
 
+## Label Conventions
+
+GitHub Labels in this project use the following prefixes, each with a defined scope:
+
+| Label prefix | Issue | PR | Notes |
+|---|---|---|---|
+| `type:` | — | Yes | Issues use the native GitHub Type field; PRs use `type:` labels for changelog generation and categorization |
+| `status:` | Yes | — | PRs already have their own state flow (Open / Draft / Merged / Closed); Issues use `status:` labels for project tracking states |
+| `in:` | Yes | Yes | Both Issues and PRs can be filtered by module |
+
+Initialize the label set with the `/init-labels` command.
+
 ## Skill Authoring Conventions
 
 When writing or updating `.agents/skills/*/SKILL.md` files and their templates, keep step numbering consistent:

package/templates/.agents/README.zh-CN.md

@@ -100,6 +100,18 @@
 4. **执行工作流**：按照 `.agents/workflows/` 中相应的工作流执行。
 5. **交接**：切换 AI 时，从模板创建交接文档。
 
+## Label 规范
+
+本项目的 GitHub Labels 按以下前缀分类，各前缀有明确的适用范围：
+
+| Label 前缀 | Issue | PR | 说明 |
+|---|---|---|---|
+| `type:` | — | Yes | Issue 使用 GitHub 原生 Type 字段；PR 无原生类型字段，通过 `type:` label 驱动 changelog 和分类 |
+| `status:` | Yes | — | PR 有自身状态流转（Open / Draft / Merged / Closed）；Issue 使用 `status:` label 标记等待反馈、已确认等项目管理状态 |
+| `in:` | Yes | Yes | Issue 和 PR 均可按模块筛选 |
+
+初始化 Label 体系：使用 `/init-labels` 命令一次性创建标准 labels。
+
 ## Skill 编写规范
 
 编写或维护 `.agents/skills/*/SKILL.md` 及其模板时，步骤编号遵循以下规则：

package/templates/.agents/skills/analyze-task/SKILL.md

@@ -1,169 +1,170 @@
 ---
 name: analyze-task
 description: >
-  分析已有任务并输出需求分析文档，支持多轮分析产物（analysis.md / analysis-r{N}.md）。
-  当用户要求分析某个任务时触发。参数：task-id。
+  Analyze an existing task and output a requirements analysis document,
+  supporting multi-round artifacts (`analysis.md` / `analysis-r{N}.md`).
+  Triggered when the user asks to analyze a task. Argument: task-id.
 ---
 
-# 分析任务
+# Analyze Task
 
-## 行为边界 / 关键规则
+## Boundary / Critical Rules
 
-- 本技能仅产出需求分析文档（`analysis.md` 或 `analysis-r{N}.md`）—— 不修改任何业务代码
-- 严格基于 `task.md` 中已有的需求、上下文和来源信息展开分析
-- 执行本技能后，你**必须**立即更新 task.md 中的任务状态
+- This skill only outputs a requirements analysis document (`analysis.md` or `analysis-r{N}.md`) and does not modify any business code
+- Base the analysis strictly on the existing requirements, context, and source information in `task.md`
+- After executing this skill, you **must** immediately update task status in task.md
 
-## 执行步骤
+## Steps
 
-### 1. 验证前置条件
+### 1. Verify Prerequisites
 
-检查必要文件：
-- `.agent-workspace/active/{task-id}/task.md` - 任务文件
+Check required files:
+- `.agent-workspace/active/{task-id}/task.md` - Task file
 
-注意：`{task-id}` 格式为 `TASK-{yyyyMMdd-HHmmss}`，例如 `TASK-20260306-143022`
+Note: `{task-id}` format is `TASK-{yyyyMMdd-HHmmss}`, for example `TASK-20260306-143022`
 
-如果缺少 `task.md`，提示用户先创建或导入任务。
+If `task.md` is missing, tell the user to create or import the task first.
 
-### 2. 确定分析轮次
+### 2. Determine the Analysis Round
 
-扫描 `.agent-workspace/active/{task-id}/` 目录中的分析产物文件：
-- 如果不存在 `analysis.md` 且不存在 `analysis-r*.md` → 本轮为第 1 轮，产出 `analysis.md`
-- 如果存在 `analysis.md` 且不存在 `analysis-r*.md` → 本轮为第 2 轮，产出 `analysis-r2.md`
-- 如果存在 `analysis-r{N}.md` → 本轮为第 N+1 轮，产出 `analysis-r{N+1}.md`
+Scan `.agent-workspace/active/{task-id}/` for analysis artifact files:
+- If neither `analysis.md` nor `analysis-r*.md` exists -> this is Round 1 and must create `analysis.md`
+- If `analysis.md` exists and no `analysis-r*.md` exists -> this is Round 2 and must create `analysis-r2.md`
+- If `analysis-r{N}.md` exists -> this is Round N+1 and must create `analysis-r{N+1}.md`
 
-记录：
-- `{analysis-round}`：本轮分析轮次
-- `{analysis-artifact}`：本轮分析产物文件名
+Record:
+- `{analysis-round}`: the current analysis round
+- `{analysis-artifact}`: the artifact filename for this round
 
-### 3. 阅读任务上下文
+### 3. Read Task Context
 
-仔细阅读 `task.md` 以理解：
-- 任务标题、描述和需求列表
-- 上下文信息（Issue、PR、分支、告警编号等）
-- 当前已知的受影响文件和约束
+Read `task.md` carefully to understand:
+- task title, description, and requirement list
+- context information (Issue, PR, branch, alert numbers, etc.)
+- currently known affected files and constraints
 
-如 `task.md` 包含以下来源字段，补充读取对应来源信息：
+If `task.md` contains these source fields, also read the corresponding source information:
 - `issue_number` - GitHub Issue
-- `codescan_alert_number` - Code Scanning 告警
-- `security_alert_number` - Dependabot 告警
+- `codescan_alert_number` - Code Scanning alert
+- `security_alert_number` - Dependabot alert
 
-### 4. 执行需求分析
+### 4. Perform Requirements Analysis
 
-遵循 `.agents/workflows/feature-development.yaml` 中的 `analysis` 步骤：
+Follow the `analysis` step in `.agents/workflows/feature-development.yaml`:
 
-**必要任务**（仅分析，不编写业务代码）：
-- [ ] 理解任务需求和目标
-- [ ] 搜索相关代码文件（**只读**）
-- [ ] 分析代码结构和影响范围
-- [ ] 识别潜在技术风险和依赖
-- [ ] 评估工作量和复杂度
+**Required tasks** (analysis only, no business code changes):
+- [ ] Understand the task requirements and goals
+- [ ] Search related code files (**read-only**)
+- [ ] Analyze code structure and impact scope
+- [ ] Identify potential technical risks and dependencies
+- [ ] Assess effort and complexity
 
-### 5. 输出分析文档
+### 5. Output Analysis Document
 
-创建 `.agent-workspace/active/{task-id}/{analysis-artifact}`。
+Create `.agent-workspace/active/{task-id}/{analysis-artifact}`.
 
-## 输出模板
+## Output Template
 
 ```markdown
-# 需求分析报告
+# Requirements Analysis Report
 
-- **分析轮次**：Round {analysis-round}
-- **产物文件**：`{analysis-artifact}`
+- **Analysis round**: Round {analysis-round}
+- **Artifact file**: `{analysis-artifact}`
 
-## 需求来源
+## Requirement Source
 
-**来源类型**：{用户描述 / GitHub Issue / Code Scanning / Dependabot / 其他}
-**来源摘要**：
-> {任务来源或关键上下文}
+**Source type**: {User description / GitHub Issue / Code Scanning / Dependabot / Other}
+**Source summary**:
+> {Task source or key context}
 
-## 需求理解
-{用自己的话重述需求以确认理解}
+## Requirement Understanding
+{Restate the requirement in your own words to confirm understanding}
 
-## 相关文件
-- `{file-path}:{line-number}` - {描述}
+## Related Files
+- `{file-path}:{line-number}` - {Description}
 
-## 影响评估
-**直接影响**：
-- {受影响的模块和文件}
+## Impact Assessment
+**Direct impact**:
+- {Affected modules and files}
 
-**间接影响**：
-- {可能受影响的其他部分}
+**Indirect impact**:
+- {Other parts that may be affected}
 
-## 技术风险
-- {风险描述和缓解思路}
+## Technical Risks
+- {Risk description and mitigation idea}
 
-## 依赖关系
-- {需要的依赖和与其他模块的协调}
+## Dependencies
+- {Required dependencies and coordination with other modules}
 
-## 工作量和复杂度评估
-- 复杂度：{高/中/低}
-- 风险等级：{高/中/低}
+## Effort and Complexity Assessment
+- Complexity: {High/Medium/Low}
+- Risk level: {High/Medium/Low}
 ```
 
-### 6. 更新任务状态
+### 6. Update Task Status
 
-获取当前时间：
+Get the current time:
 
 ```bash
 date "+%Y-%m-%d %H:%M:%S"
 ```
 
-更新 `.agent-workspace/active/{task-id}/task.md`：
-- `current_step`：requirement-analysis
-- `assigned_to`：{当前 AI 代理}
-- `updated_at`：{当前时间}
-- 记录本轮分析产物：`{analysis-artifact}`（Round `{analysis-round}`）
-- 如任务模板包含 `## 分析` 段落，更新为指向 `{analysis-artifact}` 的链接
-- 在工作流进度中标记 requirement-analysis 为已完成，并注明实际轮次（如果任务模板支持）
-- **追加**到 `## Activity Log`（不要覆盖之前的记录）：
+Update `.agent-workspace/active/{task-id}/task.md`:
+- `current_step`: requirement-analysis
+- `assigned_to`: {current AI agent}
+- `updated_at`: {current time}
+- Record the analysis artifact for this round: `{analysis-artifact}` (Round `{analysis-round}`)
+- If the task template contains a `## Analysis` section, update it to link to `{analysis-artifact}`
+- Mark requirement-analysis as complete in workflow progress and include the actual round when the task template supports it
+- **Append** to `## Activity Log` (do NOT overwrite previous entries):
   ```
   - {yyyy-MM-dd HH:mm:ss} — **Requirement Analysis (Round {N})** by {agent} — Analysis completed → {analysis-artifact}
   ```
 
-### 7. 告知用户
+### 7. Inform User
 
-> **重要**：以下「下一步」中列出的所有 TUI 命令格式必须完整输出，不要只展示当前 AI 代理对应的格式。
+> **IMPORTANT**: All TUI command formats listed below must be output in full. Do not show only the format for the current AI agent.
 
-输出格式：
+Output format:
 ```
-任务 {task-id} 分析完成。
+Analysis complete for task {task-id}.
 
-摘要：
-- 分析轮次：Round {analysis-round}
-- 相关文件：{数量}
-- 风险等级：{评估}
+Summary:
+- Analysis round: Round {analysis-round}
+- Related files: {count}
+- Risk level: {assessment}
 
-产出文件：
-- 分析报告：.agent-workspace/active/{task-id}/{analysis-artifact}
+Output file:
+- Analysis report: .agent-workspace/active/{task-id}/{analysis-artifact}
 
-下一步 - 设计技术方案：
-  - Claude Code / OpenCode：/plan-task {task-id}
-  - Gemini CLI：/agent-infra:plan-task {task-id}
-  - Codex CLI：$plan-task {task-id}
+Next step - create technical plan:
+  - Claude Code / OpenCode: /plan-task {task-id}
+  - Gemini CLI: /{{project}}:plan-task {task-id}
+  - Codex CLI: $plan-task {task-id}
 ```
 
-## 完成检查清单
+## Completion Checklist
 
-- [ ] 阅读并理解了任务文件和来源信息
-- [ ] 创建了分析文档 `.agent-workspace/active/{task-id}/{analysis-artifact}`
-- [ ] 更新了 task.md 中的 `current_step` 为 requirement-analysis
-- [ ] 更新了 task.md 中的 `updated_at` 为当前时间
-- [ ] 更新了 task.md 中的 `assigned_to`
-- [ ] 追加了 Activity Log 条目到 task.md
-- [ ] 在工作流进度中标记了 requirement-analysis 为已完成
-- [ ] 告知了用户下一步（必须展示所有 TUI 的命令格式，不要筛选）
-- [ ] **没有修改任何业务代码**
+- [ ] Read and understood the task file and source information
+- [ ] Created analysis document `.agent-workspace/active/{task-id}/{analysis-artifact}`
+- [ ] Updated `current_step` to requirement-analysis in task.md
+- [ ] Updated `updated_at` to the current time in task.md
+- [ ] Updated `assigned_to` in task.md
+- [ ] Appended an Activity Log entry to task.md
+- [ ] Marked requirement-analysis as complete in workflow progress
+- [ ] Informed the user of the next step (must include all TUI command formats; do not filter)
+- [ ] **Did not modify any business code**
 
-## 停止
+## STOP
 
-完成检查清单后，**立即停止**。等待用户审查分析结果并手动调用 `plan-task` 技能。
+After completing the checklist, **stop immediately**. Wait for the user to review the analysis result and manually invoke the `plan-task` skill.
 
-## 注意事项
+## Notes
 
-1. **前置条件**：必须已存在任务文件 `task.md`
-2. **多轮分析**：需求变化或已有分析需要修订时，使用 `analysis-r{N}.md`
-3. **职责单一**：本技能只负责分析，不设计方案、不实现代码
+1. **Prerequisite**: the task file `task.md` must already exist
+2. **Multi-round analysis**: use `analysis-r{N}.md` when requirements change or an existing analysis needs revision
+3. **Single responsibility**: this skill only handles analysis, not planning or implementation
 
-## 错误处理
+## Error Handling
 
-- 任务未找到：提示 "Task {task-id} not found, please check the task ID"
+- Task not found: output "Task {task-id} not found, please check the task ID"

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

@@ -1,122 +1,123 @@
 ---
 name: close-codescan
 description: >
-  关闭 Code Scanning（CodeQL）告警并提供有据可查的理由。
-  当用户要求关闭 Code Scanning 告警时触发。参数：告警编号。
+  Dismiss a Code Scanning (CodeQL) alert with a documented justification.
+  Triggered when the user asks to dismiss a Code Scanning alert.
+  Argument: alert number.
 ---
 
-# 关闭 Code Scanning 告警
+# Dismiss Code Scanning Alert
 
-关闭指定的 Code Scanning（CodeQL）告警并记录合理的关闭理由。
+Dismiss the specified Code Scanning (CodeQL) alert and record a justified reason.
 
-## 执行流程
+## Execution Flow
 
-### 1. 获取告警信息
+### 1. Retrieve Alert Information
 
 ```bash
 gh api repos/{owner}/{repo}/code-scanning/alerts/<alert-number>
 ```
 
-验证告警处于 `open` 状态。如果已被关闭/修复，告知用户并退出。
+Verify that the alert is in the `open` state. If it is already dismissed or fixed, inform the user and exit.
 
-### 2. 展示告警详情
+### 2. Show Alert Details
 
 ```
-Code Scanning 告警 #{alert-number}
+Code Scanning alert #{alert-number}
 
-严重程度：{security_severity_level}
-规则：{rule.id} - {rule.description}
-扫描工具：{tool.name}
-位置：{location.path}:{location.start_line}
-消息：{message}
+Severity: {security_severity_level}
+Rule: {rule.id} - {rule.description}
+Scanner: {tool.name}
+Location: {location.path}:{location.start_line}
+Message: {message}
 ```
 
-### 3. 询问关闭理由
+### 3. Ask for the Dismissal Reason
 
-提示用户选择理由：
+Ask the user to choose a reason:
 
-1. **误报 (False Positive)** - CodeQL 规则误判；代码不存在此安全问题
-2. **不会修复 (Won't Fix)** - 已知问题但基于架构或业务原因不予修复
-3. **测试代码 (Used in Tests)** - 仅在测试代码中出现，不影响生产环境安全
-4. **取消** - 不关闭告警
+1. **False Positive** - the CodeQL rule misfired and the code does not contain the security issue
+2. **Won't Fix** - the issue is known but will not be fixed due to architectural or business reasons
+3. **Used in Tests** - the issue appears only in test code and does not affect production security
+4. **Cancel** - do not dismiss the alert
 
-### 4. 要求详细说明
+### 4. Require a Detailed Explanation
 
-如果用户选择关闭（非取消），要求提供详细说明：
-- 最少 20 个字符
-- 必须清楚说明为什么可以安全关闭该告警
-- 如果是误报，说明为什么代码不存在该安全问题
-- 如果是不修复，说明技术或业务原因
+If the user chooses to dismiss the alert (not cancel), require a detailed explanation:
+- at least 20 characters
+- must clearly explain why the alert can be safely dismissed
+- if it is a false positive, explain why the code does not contain the issue
+- if it is won't fix, explain the technical or business reason
 
-### 5. 最终确认
+### 5. Final Confirmation
 
 ```
-即将关闭 Code Scanning 告警 #{alert-number}：
+About to dismiss Code Scanning alert #{alert-number}:
 
-规则：{rule.id}
-位置：{location.path}:{location.start_line}
-原因：{选择的理由}
-说明：{用户的说明}
+Rule: {rule.id}
+Location: {location.path}:{location.start_line}
+Reason: {selected reason}
+Explanation: {user explanation}
 
-确认？(y/N)
+Confirm? (y/N)
 ```
 
-### 6. 执行关闭
+### 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="{用户的说明}"
+  -f dismissed_comment="{user explanation}"
 ```
 
-**API reason 映射**（按 GitHub Code Scanning API）：
-- 误报 -> `false positive`
-- 不会修复 -> `won't fix`
-- 测试代码 -> `used in tests`
+**API reason mapping** (per the GitHub Code Scanning API):
+- False Positive -> `false positive`
+- Won't Fix -> `won't fix`
+- Used in Tests -> `used in tests`
 
-### 7. 记录到任务（如存在）
+### 7. Record in the Task (If Any)
 
-如果有关联任务（搜索 `codescan_alert_number: <alert-number>`）：
-获取当前时间：
+If a related task exists (search for `codescan_alert_number: <alert-number>`):
+Get the current time:
 
 ```bash
 date "+%Y-%m-%d %H:%M:%S"
 ```
 
-- 添加关闭记录到 task.md
-- **追加**到 `## Activity Log`（不要覆盖之前的记录）：
+- Add the dismissal record to task.md
+- **Append** to `## Activity Log` (do NOT overwrite previous entries):
   ```
   - {yyyy-MM-dd HH:mm:ss} — **Alert Closed** by {agent} — Code Scanning alert #{alert-number} dismissed: {reason}
   ```
-- 归档任务
+- Archive the task
 
-### 8. 告知用户
+### 8. Inform User
 
 ```
-Code Scanning 告警 #{alert-number} 已关闭。
+Code Scanning alert #{alert-number} dismissed.
 
-规则：{rule.id}
-位置：{location.path}:{location.start_line}
-原因：{reason}
-说明：{explanation}
+Rule: {rule.id}
+Location: {location.path}:{location.start_line}
+Reason: {reason}
+Explanation: {explanation}
 
-查看：{html_url}
+View: {html_url}
 
-注意：如有需要，可在 GitHub 上重新打开。
+Note: it can be reopened on GitHub if necessary.
 ```
 
-## 注意事项
+## Notes
 
-1. **谨慎处理高严重程度告警**：Critical/High 告警需要充分分析。建议先执行 import-codescan + analyze-task。
-2. **真实的理由**：关闭记录保存在 GitHub 中，可能会被审计。
-3. **定期复查**：已关闭的告警应定期复查。
-4. **优先修复**：关闭应作为最后手段。
+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.
+3. **Review periodically**: dismissed alerts should be re-evaluated over time.
+4. **Fix first**: dismissal should be the last resort.
 
-## 错误处理
+## Error Handling
 
-- 告警未找到：提示 "Code Scanning alert #{number} not found"
-- 已关闭：提示 "Alert #{number} is already {state}"
-- 权限错误：提示 "No permission to modify alerts"
-- 用户取消：提示 "Cancellation acknowledged"
+- Alert not found: output "Code Scanning alert #{number} not found"
+- Already closed: output "Alert #{number} is already {state}"
+- Permission error: output "No permission to modify alerts"
+- User canceled: output "Cancellation acknowledged"