AgentStack
Sign in Publish
MCP servers Skills Toolkits Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Create Migration

skill-girijashankarj-cursor-handbook-create-migration · by girijashankarj

Create a new database migration following project naming and safety rules. Use when the user asks to add a migration or create a migration for a schema change.

↗ Repository
— No reviews yet
0 installs
17 views
0.0% view→install

Install

$ agentstack add skill-girijashankarj-cursor-handbook-create-migration

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No 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.

Are you the author of Create Migration? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Skill: Create migration

Trigger

When the user asks to add a migration, create a migration for a schema change, or "migrate the DB."

Steps

  1. Clarify — Confirm the change (new table, new column, index, constraint); ensure backward compatible where possible.
  2. Naming — Use format YYYYMMDDHHMMSS_descriptive_action.sql (or project equivalent).
  3. UP — Write the forward migration (ADD COLUMN with default, CREATE INDEX CONCURRENTLY where supported).
  4. DOWN — Write the rollback; test that DOWN reverts UP cleanly.
  5. Review — No raw DELETE; use soft delete if needed; parameterized only; add index for new FK/filters.

If a step fails

| Step | Failure | Recovery | |------|---------|----------| | Step 4 | DOWN does not revert UP cleanly | Fix DOWN to match UP; test both directions; document manual steps if schema change is irreversible | | Step 5 | Review finds unsafe patterns | Rewrite migration; no raw DELETE; use soft delete; add defaults for new columns |

Rules

  • Follow .cursor/rules/database/migration-rules.mdc and schema-design rules.
  • Every table must have id, createdat, updatedat, and soft-delete column per project config.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

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.

More in Databases