Install
$ agentstack add skill-saifoelloh-golang-best-practices-skill-migration-safety ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Migration Safety
Expert-level review of database migration safety for production PostgreSQL deployments. Ensures zero-downtime schema changes, correct rollback capability, and idempotent migrations.
When to Apply
Use this skill when:
- Writing new migration files (
*.up.sql,*.down.sql) - Using GORM
AutoMigrate - Adding columns, indexes, or constraints to existing tables
- Dropping columns or tables
- Reviewing migrations before deploying to production
Zero-Downtime Migration Checklist
Before any production migration:
- [ ] NOT NULL column has DEFAULT or backfill migration first
- [ ] Indexes use
CONCURRENTLY - [ ] Migration is idempotent (
IF NOT EXISTS/IF EXISTS) - [ ]
down.sqlrollback file exists and is tested - [ ] DROP COLUMN is in a separate deploy after code references removed
- [ ] AutoMigrate is not in the application startup path
Rule Categories
| 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 |
Rules Covered (6 total)
Critical Issues (3)
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 paireddown.sql
High-Impact Patterns (2)
high-create-index-concurrently— UseCREATE INDEX CONCURRENTLYto avoid write lockshigh-idempotent-migration— UseIF NOT EXISTS/IF EXISTSfor safe re-runs
Medium Improvements (1)
medium-drop-column-deprecation— Deprecate before dropping — never drop in same deploy as code changes
Trigger Phrases
- "Review this migration"
- "Is this migration safe?"
- "ALTER TABLE"
- "ADD COLUMN / DROP COLUMN"
- "CREATE INDEX"
- "AutoMigrate"
- "Schema change"
- "Zero-downtime migration"
Related Skills
- [query-performance](../query-performance/SKILL.md) — For index design (partial, composite)
- [postgresql-syntax](../postgresql-syntax/SKILL.md) — For correct DDL SQL syntax
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: saifoelloh
- Source: saifoelloh/golang-best-practices-skill
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.