メニュー
Review schema and migration changes for safety, reversibility, rollout risk, and data integrity. Trigger when schema files or migrations change.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Turn a specification into a concrete architecture with stable contracts, file boundaries, ownership, and risk analysis. Use this when acting as the architecture writer for a task.
Run the project verification stack after code changes. Trigger on code changes and stop on the first failure, fix it, then rerun the full stack from the top.
Verify that newly created files follow the repo's existing directory layout, naming conventions, and export patterns. Trigger when a new file is created.
Break architecture into execution-ready sub-tasks with clear ownership, dependencies, and contract references. Use this when acting as the planner for a task.
Use Playwright for browser automation, UI validation, E2E tests, and interaction debugging. Useful for flows that need real page navigation, assertions, screenshots, or request interception.
Final merge-readiness check after gates pass. Confirms verification is green, changed files are clean, and obvious release blockers are gone before merge.
| name | schema-migration-review |
| description | Review schema and migration changes for safety, reversibility, rollout risk, and data integrity. Trigger when schema files or migrations change. |
| owner | any |
| trigger | schema_changed |
| version | 2 |
Use this when schema or migration files change.
NOT NULL additions on existing dataThis skill is about migration safety, not just scanning for SQL keywords.
Before finalizing, for each risk you report, cite the exact migration line(s) that support it, state whether rollback is possible, and note any required deployment sequencing or compatibility checks. If a point cannot be verified from the files, say so explicitly instead of inferring. Do not report risks that cannot be tied to specific lines.