export-db-indexes
Skill2 starsChanged 7 months agoMITView on GitHub
扫描 ORM 模型文件,对比线上表结构,生成增量 ALTER TABLE DDL 脚本,并附带真实业务查询 SQL 注释供 DBA Review。
- Deletes or force-pushes
In this repository26 other files it gives its agents.
- advise-tech-stackSkill
- commit-with-affectsSkill
- db-dev-guideSkill
- frontend-dev-guideSkill
- frontend-ux-evaluatorSkill
- generate-pr-descriptionSkill
- generate-test-from-impactSkill
- generate-test-skeletonSkill
- lock-global-conventionsSkill
- plan-component-hierarchySkill
- plan-page-mapSkill
- proposal-reviewSkill
- propose-workflow-improvementsSkill
- pr-self-reviewSkill
- record-decisionSkill
- review-guardrailsSkill
- run-pending-specsSkill
- run-testsSkill
- scan-bundle-bloatSkill
- scan-code-hygieneSkill
- scan-dead-routesSkill
- scan-frontend-qualitySkill
- scan-orphan-componentsSkill
- scan-unused-exportsSkill
- sync-llm-contextSkill
- verify-specSkill
The file
Files
Export DB Indexes Skill
触发时机
dev-flowStep 7:修改了 ORM 模型、migration 或 schema 文件后production-release第四步:数据库差异化导出- 用户手动触发:提及"导出数据库差异"、"生成 DDL"
执行步骤
Step 1:扫描 ORM 模型
读取项目 ORM 模型文件(路径来自 project.config.json → tech_stack.backend_path),提取:
- 所有表定义
- 字段类型、约束、注释
- 索引定义(包括复合索引、前缀索引)
- 表级元数据(引擎、字符集、表注释)
Step 2:对比线上结构
通过以下方式获取线上(或 baseline)表结构:
SHOW CREATE TABLE {table_name};
-- 或
SELECT * FROM information_schema.COLUMNS WHERE TABLE_NAME = '{table_name}';Step 3:生成增量 DDL
对每个有差异的表,生成:
ALTER TABLE语句(新增字段、修改字段、新增索引)- 每条 DDL 前附带
-- 业务含义说明注释 - 每条 DDL 后附带对应的真实业务查询 SQL(Query SQL),说明该索引会被哪种查询用到
输出格式示例:
-- [新增字段] user_level: 用户等级,用于会员分层筛选
ALTER TABLE user_info ADD COLUMN user_level TINYINT NOT NULL DEFAULT 0 COMMENT '用户等级';
-- [新增索引] idx_user_level: 支持按用户等级的批量查询
-- Query SQL: SELECT id, name FROM user_info WHERE user_level = ? LIMIT 100;
ALTER TABLE user_info ADD INDEX idx_user_level (user_level);Step 4:生成回滚 DDL
对每条正向 DDL,同步生成对应的回滚语句,写入独立的回滚文件。
回滚规则:
| 正向操作 | 回滚操作 |
ADD COLUMN col | DROP COLUMN col |
ADD INDEX idx | DROP INDEX idx |
MODIFY COLUMN col TYPE_A → TYPE_B | MODIFY COLUMN col TYPE_A(恢复原类型) |
CREATE TABLE | DROP TABLE IF EXISTS |
回滚文件格式:
-- 回滚脚本:对应 db_migration_{YYYYMMDD}.sql
-- 执行顺序:与正向 DDL 相反(后加的先回滚)
-- [回滚] 删除索引 idx_user_level
DROP INDEX idx_user_level ON user_info;
-- [回滚] 删除字段 user_level
ALTER TABLE user_info DROP COLUMN user_level;Step 5:输出报告
将生成的 DDL 写入两个临时文件:
tmp/db_migration_{YYYYMMDD}.sql— 正向 DDL(上线用)tmp/db_rollback_{YYYYMMDD}.sql— 回滚 DDL(回退用)
并在对话中输出摘要:
## 数据库增量导出报告
| 表名 | 变更类型 | 详情 |
|------|---------|------|
| user_info | 新增字段 | user_level (tinyint) |
| order_record | 新增索引 | idx_status_created |
正向 DDL:tmp/db_migration_{YYYYMMDD}.sql
回滚 DDL:tmp/db_rollback_{YYYYMMDD}.sql
⚠️ 请交由 DBA Review 后在对应环境执行,严禁直接在生产执行未经 Review 的 DDL。
⚠️ 回滚脚本请妥善保存,在上线后 24 小时内保持可执行状态。强制约束
- MUST 输出的 DDL 必须是
ALTER TABLE格式,禁止输出DROP TABLE或CREATE TABLE(除非是全新表) - MUST 每条 DDL 后必须附带真实 Query SQL 注释
- MUST 同时生成正向 DDL 和回滚 DDL,缺少回滚文件视为未完成
- MUST 写入
tmp/目录,不得放在项目根目录 - NEVER 在无 DBA Review 的情况下直接在生产数据库执行任何 DDL
- NEVER 在回滚 DDL 中生成
DROP TABLE(除非正向操作是 CREATE TABLE,且表为新建)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

