ai-engineering-init 1.3.4 → 1.4.0

package/.claude/skills/mysql-debug/SKILL.md

@@ -0,0 +1,364 @@
+---
+name: mysql-debug
+description: |
+  MySQL 数据库查询调试技能。通过 mysql CLI 直接查询本地 MySQL 数据库，配合日志进行 Bug 排查。
+  Bug 修复时自动评估是否需要查库，从日志中提取数据库名（租户ID），支持手动指定数据库。
+
+  触发场景：
+  - 结合日志排查 Bug 时需要查询数据库验证数据
+  - 检查数据库中某条记录的实际值
+  - 验证 SQL 执行结果是否符合预期
+  - 排查数据不一致、数据丢失、数据异常问题
+  - 需要查看表结构、索引、数据分布
+
+  触发词：查数据库、查表、执行SQL、查记录、mysql查询、数据库排查、验证数据、查数据、db查询、数据库调试
+---
+
+# MySQL 数据库查询调试技能
+
+## 概述
+
+本技能用于在 Bug 排查过程中直接查询 MySQL 数据库，验证数据状态。配合日志分析定位问题根因。
+
+**核心能力**：
+1. 智能判断 Bug 是否需要查库（明显代码错误跳过）
+2. 从日志自动提取数据库名（租户 ID = 数据库名）
+3. 只读查询，安全排查
+
+---
+
+## 首次使用引导（必须执行）
+
+当本技能被激活时，**必须先执行以下两项检查**，任一不通过则输出引导提示并停止查库操作：
+
+### 检查 1：配置文件是否就绪
+
+读取 `.claude/mysql-config.json`，确定当前环境（用户指定 或 `default` 字段），检查该环境的 password 是否仍为占位符 `YOUR_PASSWORD`：
+
+```
+如果文件不存在 或 当前环境的 password == "YOUR_PASSWORD"：
+  → 输出引导提示（见下方模板），不执行查库
+```
+
+### 检查 2：mysql CLI 是否可用
+
+执行 `which mysql`，检查是否返回有效路径：
+
+```
+如果 mysql 命令不存在：
+  → 输出引导提示（见下方模板），不执行查库
+```
+
+### 引导提示模板
+
+当检查不通过时，输出以下提示：
+
+```
+⚠️ 数据库查询功能需要先完成配置：
+
+1. 编辑 .claude/mysql-config.json，填入你的 MySQL 连接信息：
+   配置文件支持多环境（local / dev / prod），至少配置一个环境：
+   - host: 数据库地址
+   - port: 端口（默认 3306）
+   - user: 用户名
+   - password: 数据库密码（替换 YOUR_PASSWORD）
+
+2. 安装 MySQL 客户端：
+   brew install mysql-client
+
+完成后重新触发即可使用数据库查询辅助排查。
+```
+
+> 引导提示输出后，Bug 排查仍可继续（走 bug-detective 纯代码分析路径），只是跳过数据库查询环节。
+
+---
+
+## 多环境支持
+
+### 配置文件结构
+
+`.claude/mysql-config.json` 支持多环境配置：
+
+```json
+{
+  "environments": {
+    "local": { "host": "127.0.0.1", "port": 3306, "user": "root", "password": "xxx" },
+    "dev":   { "host": "dev-db.example.com", "port": 3306, "user": "dev_user", "password": "xxx" },
+    "prod":  { "host": "prod-db.example.com", "port": 3306, "user": "readonly", "password": "xxx" }
+  },
+  "default": "local"
+}
+```
+
+### 环境选择规则
+
+| 优先级 | 来源 | 示例 |
+|--------|------|------|
+| 1（最高） | 用户对话中指定 | "连 dev 环境查一下"、"用生产库看看" |
+| 2 | 配置文件 `default` 字段 | `"default": "local"` |
+
+### 环境关键词映射
+
+用户说的话 → 对应环境名：
+
+| 用户说法 | 环境 |
+|---------|------|
+| "本地"、"local"、"本地环境" | `local` |
+| "开发"、"dev"、"测试环境"、"开发环境" | `dev` |
+| "生产"、"prod"、"线上"、"正式环境" | `prod` |
+
+### 连接示例
+
+```bash
+# 用户说"连 dev 环境查一下 order_info"
+# → 读取 environments.dev 的连接信息 + 日志提取的数据库名
+mysql -h dev-db.example.com -P 3306 -u dev_user -p'xxx' 546198574447230976 -e "SELECT ..."
+```
+
+---
+
+## 核心流程：是否需要查库？
+
+### 决策树（Bug 修复时必须先评估）
+
+```
+用户报告 Bug / 提供日志
+  │
+  ├─ 明显的代码错误？ ──→ ✅ 不需要查库，直接修复
+  │   - NPE 且代码中未做空判断
+  │   - 语法错误、拼写错误
+  │   - 类型转换错误（ClassCastException）
+  │   - 缺少 import、注解遗漏
+  │   - 方法签名不匹配
+  │
+  ├─ 数据相关的问题？ ──→ 🔍 需要查库
+  │   - "查不到数据"、"数据为空"
+  │   - "数量不对"、"金额不对"
+  │   - SQL 相关异常（DataIntegrityViolation、DuplicateKey）
+  │   - 关联查询结果异常
+  │   - 状态流转异常（订单状态不对等）
+  │
+  ├─ 不确定是代码还是数据？ ──→ 🔍 需要查库确认
+  │   - 逻辑正确但结果错误
+  │   - 特定租户/特定数据才出现的 Bug
+  │   - 生产有问题但本地无法复现
+  │
+  └─ 配置/环境问题？ ──→ ✅ 不需要查库
+      - 启动失败、Bean 创建异常
+      - 配置文件错误
+      - 依赖版本冲突
+```
+
+### 评估输出格式
+
+在 Bug 修复响应中，先输出评估结论：
+
+```
+📊 数据库查询评估：需要查库
+理由：日志显示 order_info 查询返回空，需要确认数据是否存在
+数据库：546198574447230976（从日志提取）
+```
+
+或：
+
+```
+📊 数据库查询评估：不需要查库
+理由：明显的 NPE，代码中 getUserInfo() 返回值未做空判断
+```
+
+---
+
+## 从日志提取数据库名
+
+### 日志格式说明
+
+本项目的日志格式：
+
+```
+2026-03-04 10:21:40.902,-,546198574447230976,, DEBUG 94396 --- [  XNIO-1 task-3] n.x.f.c.request.RequestLoggingFilter : 47  : >>> GET /api/v2/web/xxx
+```
+
+各字段含义：
+
+```
+时间戳                    ,-,租户ID（=数据库名）,, 日志级别 PID --- [线程名] 类名 : 行号 : 日志内容
+```
+
+### 提取规则
+
+1. **自动提取**：从日志行中匹配 `,-,(\d{15,19}),,` 模式，提取的数字即为数据库名
+2. **手动指定**：用户直接说"查 546198574447230976 库"或"数据库名是 xxx"
+3. **优先级**：手动指定 > 日志提取 > 配置文件 default
+
+### 提取示例
+
+```
+日志：2026-03-04 10:21:40.902,-,546198574447230976,, DEBUG ...
+                                ↑
+                          数据库名 = 546198574447230976
+```
+
+连接时使用：
+```bash
+mysql -h 127.0.0.1 -P 3306 -u root -p'password' 546198574447230976 -e "SELECT ..."
+```
+
+---
+
+## 查询执行
+
+### 连接方式
+
+读取 `.claude/mysql-config.json` 获取 host/port/user/password，数据库名从日志提取或用户指定：
+
+```bash
+# 从配置读取连接信息 + 动态数据库名
+mysql -h {host} -P {port} -u {user} -p'{password}' {database_from_log} -e "{SQL}"
+```
+
+### 常用排查查询模板
+
+#### 查看表结构
+```sql
+DESCRIBE table_name;
+SHOW CREATE TABLE table_name;
+```
+
+#### 按 ID 查记录
+```sql
+SELECT * FROM table_name WHERE id = {id} AND del_flag = 2;
+```
+
+#### 查看最近修改的数据
+```sql
+SELECT * FROM table_name
+WHERE uptime >= '{log_timestamp}'
+ORDER BY uptime DESC
+LIMIT 20;
+```
+
+#### 检查关联数据一致性
+```sql
+SELECT a.id, b.id AS related_id
+FROM table_a a
+LEFT JOIN table_b b ON a.related_id = b.id
+WHERE a.id = {id} AND b.id IS NULL;
+```
+
+#### 统计数据分布
+```sql
+SELECT status, COUNT(*) as cnt
+FROM table_name
+WHERE del_flag = 2
+GROUP BY status;
+```
+
+#### 查看某时间段的操作记录
+```sql
+SELECT * FROM table_name
+WHERE crtime BETWEEN '{start}' AND '{end}'
+ORDER BY crtime DESC
+LIMIT 50;
+```
+
+---
+
+## 安全规范（强制执行，违反即终止）
+
+### 允许执行的 SQL（白名单）
+
+**只允许以下语句类型**：
+- `SELECT` — 查询数据
+- `DESCRIBE` / `DESC` — 查看表结构
+- `SHOW` — 查看建表语句、索引、状态等
+- `EXPLAIN` — 分析执行计划
+
+### 禁止执行的 SQL（黑名单）
+
+**DDL 操作 — 全部禁止**：
+- `CREATE TABLE / VIEW / INDEX / DATABASE`
+- `ALTER TABLE / COLUMN`
+- `DROP TABLE / VIEW / INDEX / DATABASE`
+- `TRUNCATE TABLE`
+- `RENAME TABLE`
+
+**DML 写操作 — 全部禁止**：
+- `INSERT` — 禁止插入数据
+- `UPDATE` — 禁止更新数据
+- `DELETE` — 禁止删除数据
+- `REPLACE` — 禁止替换数据
+
+**权限/管理操作 — 全部禁止**：
+- `GRANT / REVOKE`
+- `SET GLOBAL`
+- `FLUSH`
+
+### 敏感 SQL 拦截（执行前必须分析）
+
+在执行任何 SQL 之前，必须进行安全分析。遇到以下情况时，**不执行 SQL，改为输出分析结果并询问用户**：
+
+| 风险类型 | 检测规则 | 处理方式 |
+|---------|---------|---------|
+| 无 WHERE 全表扫描 | `SELECT * FROM xxx` 无 WHERE 子句 | 提醒用户加条件，或自动加 `LIMIT 10` |
+| 大范围查询 | WHERE 条件覆盖范围过大（如 `del_flag = 2`） | 提醒加更精确条件，强制 `LIMIT 50` |
+| 多表 JOIN 无条件 | JOIN 无 ON 条件（笛卡尔积） | 拒绝执行，提示补充 JOIN 条件 |
+| 子查询嵌套过深 | 超过 3 层嵌套子查询 | 输出 SQL 让用户确认后再执行 |
+| 敏感表查询 | 涉及用户密码表、密钥表 | 输出脱敏后的 SQL 分析，不直接查询 |
+
+### 执行前检查流程
+
+```
+收到/构造 SQL
+  │
+  ├─ 是否在白名单内？ ──→ 否 → 拒绝执行，输出原因
+  │
+  ├─ 是否命中敏感规则？ ──→ 是 → 输出风险分析，询问用户
+  │
+  ├─ 是否包含 LIMIT？ ──→ 否 → 自动追加 LIMIT 50
+  │
+  └─ 通过所有检查 → 执行 SQL
+```
+
+### 查询结果安全
+
+- 查询必须加 `LIMIT`（默认 LIMIT 50）防止返回过多数据
+- 不在输出中暴露密码、手机号（phone）、身份证（id_card）等敏感字段
+- 查询结果中的敏感字段用 `***` 脱敏展示
+- 如需修改数据，**只输出 SQL 语句让用户手动执行**，不代为执行
+
+### 配置文件安全
+
+- `.claude/mysql-config.json` 已加入 `.gitignore`，禁止提交到版本库
+
+---
+
+## 与 bug-detective 配合
+
+本技能是 `bug-detective` 的数据层扩展。当 bug-detective 被触发时，会自动评估是否需要同时激活 mysql-debug：
+
+| 步骤 | bug-detective | mysql-debug |
+|------|--------------|-------------|
+| 1 | 分析日志、定位异常层 | 评估是否需要查库 |
+| 2 | 识别涉及的表和查询 | 从日志提取数据库名 |
+| 3 | 推断可能原因 | 执行 SQL 验证数据 |
+| 4 | 给出修复方案 | 用数据证实/排除假设 |
+
+典型联合使用：
+```
+用户："订单查询接口返回空数据，日志如下..."
+日志：2026-03-04 10:21:40.902,-,546198574447230976,, ERROR ...
+
+→ 评估：需要查库（数据返回空，需确认数据是否存在）
+→ 提取数据库：546198574447230976
+→ 执行：SELECT * FROM order_info WHERE id = xxx AND del_flag = 2
+→ 发现：del_flag = 1（已删除），用户操作了删除但不知情
+→ 修复方案：恢复数据 / 检查前端删除按钮权限
+```
+
+---
+
+## 注意
+
+- 本技能专注于**查询数据库辅助排查**，不涉及建表、迁移等操作（请使用 `database-ops`）
+- 如果是纯代码错误（NPE、语法错误等）不需要查库，请使用 `bug-detective`
+- 如果是 SQL 性能问题（慢查询），请使用 `performance-doctor`

package/.claude/skills/openspec-apply-change/SKILL.md

@@ -1,6 +1,15 @@
 ---
 name: openspec-apply-change
-description: Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
+description: |
+  Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
+
+  触发场景：
+  - 需要实现 OpenSpec 变更中的任务
+  - 执行变更制品中定义的实现步骤
+  - 将规格和设计转化为实际代码
+  - 逐个完成 tasks.md 中的待办事项
+
+  触发词：实现任务、开始实现、opsx:apply、openspec apply、执行变更、开始编码、实现变更
 license: MIT
 compatibility: Requires openspec CLI.
 metadata:

package/.claude/skills/openspec-archive-change/SKILL.md

@@ -1,6 +1,14 @@
 ---
 name: openspec-archive-change
-description: Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
+description: |
+  Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
+
+  触发场景：
+  - 变更实现完毕，需要归档保存
+  - 完成的变更需要移入 archive 目录
+  - 项目决策记录需要持久化保存
+
+  触发词：归档变更、归档、opsx:archive、openspec archive、完成变更、存档、归档完成
 license: MIT
 compatibility: Requires openspec CLI.
 metadata:

package/.claude/skills/openspec-bulk-archive-change/SKILL.md

@@ -1,6 +1,14 @@
 ---
 name: openspec-bulk-archive-change
-description: Archive multiple completed changes at once. Use when archiving several parallel changes.
+description: |
+  Archive multiple completed changes at once. Use when archiving several parallel changes.
+
+  触发场景：
+  - 多个变更同时完成，需要批量归档
+  - 清理多个已完成的并行变更
+  - 需要处理多个变更之间的规格冲突后统一归档
+
+  触发词：批量归档、全部归档、opsx:bulk-archive、一起归档、归档所有变更、批量存档
 license: MIT
 compatibility: Requires openspec CLI.
 metadata:

package/.claude/skills/openspec-continue-change/SKILL.md

@@ -1,6 +1,14 @@
 ---
 name: openspec-continue-change
-description: Continue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue their workflow.
+description: |
+  Continue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue their workflow.
+
+  触发场景：
+  - 需要继续推进已有变更的下一个制品
+  - 上次中断后恢复变更工作
+  - 逐步创建变更的 proposal/specs/design/tasks
+
+  触发词：继续变更、继续、opsx:continue、openspec continue、下一步、推进变更、继续工作
 license: MIT
 compatibility: Requires openspec CLI.
 metadata:

package/.claude/skills/openspec-explore/SKILL.md

@@ -1,6 +1,15 @@
 ---
 name: openspec-explore
-description: Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
+description: |
+  Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
+
+  触发场景：
+  - 需要在实现前先探索和思考问题
+  - 比较多种技术方案的优劣
+  - 调查代码库中的现有架构和模式
+  - 在变更实现过程中遇到困惑需要深入分析
+
+  触发词：探索、opsx:explore、openspec explore、想一想、分析问题、调研方案、头脑风暴
 license: MIT
 compatibility: Requires openspec CLI.
 metadata:

package/.claude/skills/openspec-ff-change/SKILL.md

@@ -1,6 +1,14 @@
 ---
 name: openspec-ff-change
-description: Fast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually.
+description: |
+  Fast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually.
+
+  触发场景：
+  - 需要快速一次性生成所有变更制品
+  - 跳过逐步创建，直接生成 proposal/specs/design/tasks
+  - 想快速启动一个变更并立即进入实现阶段
+
+  触发词：快速创建、快进、opsx:ff、openspec ff、一键生成、快速开始、fast forward
 license: MIT
 compatibility: Requires openspec CLI.
 metadata:

package/.claude/skills/openspec-new-change/SKILL.md

@@ -1,6 +1,14 @@
 ---
 name: openspec-new-change
-description: Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.
+description: |
+  Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.
+
+  触发场景：
+  - 需要创建一个新的 OpenSpec 变更
+  - 开始一个新功能或修复的结构化工作流
+  - 初始化变更目录并查看第一个制品模板
+
+  触发词：新建变更、新变更、opsx:new、openspec new、创建变更、开始新功能、新增变更
 license: MIT
 compatibility: Requires openspec CLI.
 metadata:

package/.claude/skills/openspec-onboard/SKILL.md

@@ -1,6 +1,14 @@
 ---
 name: openspec-onboard
-description: Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.
+description: |
+  Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.
+
+  触发场景：
+  - 首次使用 OpenSpec，需要引导式教学
+  - 想通过实际操作学习 OpenSpec 完整工作流
+  - 需要了解 OpenSpec 的所有命令和流程
+
+  触发词：入门、onboard、opsx:onboard、openspec 教程、学习 openspec、新手引导、openspec 入门
 license: MIT
 compatibility: Requires openspec CLI.
 metadata:
@@ -72,55 +80,13 @@ git log --oneline -10 2>/dev/null || echo "No git history"
 
 ### Present Suggestions
 
-From your analysis, present 3-4 specific suggestions:
-
-```
-## Task Suggestions
-
-Based on scanning your codebase, here are some good starter tasks:
-
-**1. [Most promising task]**
-   Location: `src/path/to/file.ts:42`
-   Scope: ~1-2 files, ~20-30 lines
-   Why it's good: [brief reason]
-
-**2. [Second task]**
-   Location: `src/another/file.ts`
-   Scope: ~1 file, ~15 lines
-   Why it's good: [brief reason]
-
-**3. [Third task]**
-   Location: [location]
-   Scope: [estimate]
-   Why it's good: [brief reason]
+From your analysis, present 3-4 specific suggestions with location, scope estimate, and brief reason. Include a "Something else?" option. Let the user pick a number or describe their own.
 
-**4. Something else?**
-   Tell me what you'd like to work on.
-
-Which task interests you? (Pick a number or describe your own)
-```
-
-**If nothing found:** Fall back to asking what the user wants to build:
-> I didn't find obvious quick wins in your codebase. What's something small you've been meaning to add or fix?
+**If nothing found:** Fall back to asking what the user wants to build.
 
 ### Scope Guardrail
 
-If the user picks or describes something too large (major feature, multi-day work):
-
-```
-That's a valuable task, but it's probably larger than ideal for your first OpenSpec run-through.
-
-For learning the workflow, smaller is better—it lets you see the full cycle without getting stuck in implementation details.
-
-**Options:**
-1. **Slice it smaller** - What's the smallest useful piece of [their task]? Maybe just [specific slice]?
-2. **Pick something else** - One of the other suggestions, or a different small task?
-3. **Do it anyway** - If you really want to tackle this, we can. Just know it'll take longer.
-
-What would you prefer?
-```
-
-Let the user override if they insist—this is a soft guardrail.
+If the user picks something too large (major feature, multi-day work), suggest slicing smaller or picking something else. Offer three options: slice it, pick another, or do it anyway. This is a soft guardrail—let the user override if they insist.
 
 ---
 
@@ -200,40 +166,7 @@ The proposal captures **why** we're making this change and **what** it involves
 I'll draft one based on our task.
 ```
 
-**DO:** Draft the proposal content (don't save yet):
-
-```
-Here's a draft proposal:
-
----
-
-## Why
-
-[1-2 sentences explaining the problem/opportunity]
-
-## What Changes
-
-[Bullet points of what will be different]
-
-## Capabilities
-
-### New Capabilities
-- `<capability-name>`: [brief description]
-
-### Modified Capabilities
-<!-- If modifying existing behavior -->
-
-## Impact
-
-- `src/path/to/file.ts`: [what changes]
-- [other files if applicable]
-
----
-
-Does this capture the intent? I can adjust before we save it.
-```
-
-**PAUSE** - Wait for user approval/feedback.
+**DO:** Draft the proposal with sections: Why, What Changes, Capabilities (New/Modified), Impact. Show the draft and **PAUSE** for user approval/feedback before saving.
 
 After approval, save the proposal:
 ```bash
@@ -304,37 +237,7 @@ The design captures **how** we'll build it—technical decisions, tradeoffs, app
 For small changes, this might be brief. That's fine—not every change needs deep design discussion.
 ```
 
-**DO:** Draft design.md:
-
-```
-Here's the design:
-
----
-
-## Context
-
-[Brief context about the current state]
-
-## Goals / Non-Goals
-
-**Goals:**
-- [What we're trying to achieve]
-
-**Non-Goals:**
-- [What's explicitly out of scope]
-
-## Decisions
-
-### Decision 1: [Key decision]
-
-[Explanation of approach and rationale]
-
----
-
-For a small task, this captures the key decisions without over-engineering.
-```
-
-Save to `openspec/changes/<name>/design.md`.
+**DO:** Draft design.md with sections: Context, Goals/Non-Goals, Decisions. Keep it brief for small changes. Save to `openspec/changes/<name>/design.md`.
 
 ---
 
@@ -496,25 +399,7 @@ Exit gracefully without pressure.
 
 ### User just wants command reference
 
-If the user says they just want to see the commands or skip the tutorial:
-
-```
-## OpenSpec Quick Reference
-
-| Command | What it does |
-|---------|--------------|
-| `/opsx:explore` | Think through problems (no code changes) |
-| `/opsx:new <name>` | Start a new change, step by step |
-| `/opsx:ff <name>` | Fast-forward: all artifacts at once |
-| `/opsx:continue <name>` | Continue an existing change |
-| `/opsx:apply <name>` | Implement tasks |
-| `/opsx:verify <name>` | Verify implementation |
-| `/opsx:archive <name>` | Archive when done |
-
-Try `/opsx:new` to start your first change, or `/opsx:ff` if you want to move fast.
-```
-
-Exit gracefully.
+If the user says they just want to see the commands or skip the tutorial, show the Command Reference table from Phase 11 and exit gracefully.
 
 ---
 

package/.claude/skills/openspec-sync-specs/SKILL.md

@@ -1,6 +1,14 @@
 ---
 name: openspec-sync-specs
-description: Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.
+description: |
+  Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.
+
+  触发场景：
+  - 需要将变更中的增量规格同步到主规格
+  - 变更的 delta spec 需要合并到 openspec/specs 目录
+  - 在归档前手动同步规格变更
+
+  触发词：同步规格、同步specs、opsx:sync、openspec sync、合并规格、同步变更规格
 license: MIT
 compatibility: Requires openspec CLI.
 metadata:

package/.claude/skills/openspec-verify-change/SKILL.md

@@ -1,6 +1,14 @@
 ---
 name: openspec-verify-change
-description: Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.
+description: |
+  Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.
+
+  触发场景：
+  - 实现完成后需要验证是否与规格一致
+  - 归档前检查任务完成度和代码正确性
+  - 需要生成变更的完整性/正确性/一致性报告
+
+  触发词：验证变更、验证、opsx:verify、openspec verify、检查实现、校验变更、验收
 license: MIT
 compatibility: Requires openspec CLI.
 metadata: