菜单
Database migration safety review for GORM + PostgreSQL. Use when writing or reviewing schema changes, AutoMigrate usage, ALTER TABLE statements, or index creation. Covers zero-downtime patterns, NOT NULL backfill, CONCURRENTLY indexes, idempotency, and rollback files.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Comprehensive Go + GORM + PostgreSQL review meta-skill. Coordinates 9 specialized domain skills for fullstack Go application audits. Covers concurrency, architecture, idioms, queries, SQL performance, and migration safety.
Unified Go + GORM + PostgreSQL error handling review. Covers error wrapping, context propagation, PostgreSQL error codes (23505, 40001), errors.Is/As mapping, and retry logic. Ensures proper error chains and robust database failure recovery.
GORM ORM query pattern review for PostgreSQL. Use when reviewing or writing Go database code using GORM — covers N+1, Preload vs Joins, transactions, error checking, Save vs Updates, and context propagation. Trigger on any GORM method usage.
PostgreSQL SQL syntax review for Go/GORM projects. Use when writing or reviewing raw SQL used via db.Raw(), db.Exec(), or migrations. Covers placeholder style, reserved keyword quoting, RETURNING, ILIKE, JSONB operators, and type casting. Don't use for MySQL or SQLite.
GORM + PostgreSQL query performance review. Use when optimizing slow queries, designing indexes, analyzing N+1 patterns, or configuring connection pools. Trigger on "slow", "optimize", "index", "EXPLAIN", "N+1", or performance degradation.
Clean Architecture audit for Go services. Use when reviewing layered architecture, dependency rules, or gRPC/usecase/repository patterns. Ensures proper separation of concerns and dependency inversion.
| name | gorm-sql-migration-safety |
| description | Database migration safety review for GORM + PostgreSQL. Use when writing or reviewing schema changes, AutoMigrate usage, ALTER TABLE statements, or index creation. Covers zero-downtime patterns, NOT NULL backfill, CONCURRENTLY indexes, idempotency, and rollback files. |
| license | MIT |
| metadata | {"author":"saifoelloh","version":"1.0.0","parent_skill":"gorm-sql-best-practices","sources":["PostgreSQL 16 Official Documentation","Braintree Engineering: Safe Operations for High-Volume PostgreSQL","golang-migrate documentation"],"last_updated":"2026-03-13"} |
Expert-level review of database migration safety for production PostgreSQL deployments. Ensures zero-downtime schema changes, correct rollback capability, and idempotent migrations.
Use this skill when:
*.up.sql, *.down.sql)AutoMigrateBefore any production migration:
CONCURRENTLYIF NOT EXISTS / IF EXISTS)down.sql rollback file exists and is tested| Priority | Count | Focus |
|---|---|---|
| Critical | 3 | AutoMigrate in production, NOT NULL backfill, missing rollback |
| High | 2 | CONCURRENTLY indexes, idempotent migrations |
| Medium | 1 | DROP COLUMN deprecation period |
critical-no-automigrate-production — Never run AutoMigrate in production startup pathcritical-not-null-backfill — NOT NULL column addition requires 3-step migrationcritical-always-provide-rollback — Every migration must have a paired down.sqlhigh-create-index-concurrently — Use CREATE INDEX CONCURRENTLY to avoid write lockshigh-idempotent-migration — Use IF NOT EXISTS / IF EXISTS for safe re-runsmedium-drop-column-deprecation — Deprecate before dropping — never drop in same deploy as code changes