菜单
Database migration/schema-change safety lens over a feature's diff — read-only. Appended to review-and-simplify's lens registry by the api-review pack. Also usable standalone.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Ingest a raw source into the project's OKF knowledge bundle — distill it into concept pages, refresh the index, and log the change. keel's compounding "LLM wiki" loop.
Use when implementation is complete, gates pass, and you need to decide how to integrate the work — presents structured options (merge, PR, keep, discard) and handles the chosen workflow, including worktree cleanup. Closes the SDD cycle after review-and-simplify.
Use when executing implementation plans with independent tasks in the current session
Orchestrates the implement-feature, evaluator, fix-runner loop for the active feature until all Criterios de Aceitacao are met and quality gates are green.
Use after the plan is approved to break the active feature's plan into a concrete task checklist, written into specs/<feature>/tasks.md from the tasks template.
Use while implementing a feature that has retries, queues, background jobs, external calls, or any critical path an on-call engineer will need to reason about in production. Invoke when adding a new endpoint, dependency, or async flow, and before considering such a feature done — instrumentation is developed alongside the code, like tests, not bolted on after.
| name | migration-safety |
| description | Database migration/schema-change safety lens over a feature's diff — read-only. Appended to review-and-simplify's lens registry by the api-review pack. Also usable standalone. |
When: dispatched by review-and-simplify as one of its parallel lenses, on the feature's diff, in projects where the api-review pack is installed. Also usable standalone for a focused migration pass.
Scope: schema and migration changes only in the feature's tree-snapshot diff (git diff BASE_TREE HEAD_TREE, per subagent-driven-development's no-commit-rule snapshotting) or, if no snapshots exist, the working tree diff — migration files, schema.prisma, SQL DDL, ORM entity/column changes. Never the whole repo. If the diff contains no schema/migration change, report "no migration-relevant changes" and stop — do not manufacture findings.
Output: findings by severity (Critical/Important/Minor) with file:line, reported inline. Makes NO edits.
Judge migration safety against existing data and a live deploy — the concern is "will applying this to a populated production DB lose data, fail, or lock a table", distinct from perf-review's query-efficiency concern (N+1, missing index on a hot read). Flag only what the changed migration/schema introduces.
NOT NULL column to a populated table with no default and no backfill step; making an existing nullable column NOT NULL before existing NULLs are backfilled — the migration fails on real data.UNIQUE/CHECK/foreign-key constraint without first proving or cleaning existing rows that would violate it.perf-review.Weigh blast radius: a DROP COLUMN on a live table or a NOT NULL add without backfill is Critical; a missing down-migration on a brand-new table with no data is Minor. Do not restate what a migration linter (e.g. an online-DDL checker) already gates — this lens is for the judgment those miss (is this column actually still in use? is the backfill correct?).
Next: findings return to review-and-simplify, which aggregates them with the other lenses; Critical/Important must be fixed before the pre-commit gate.