Skip to content
Agentmart
Submit a tool

database-migrations

Database migration planning and review workflow.

Skill by JunMystery

IndexedMIT
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/junmystery-database-migrations

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Database migration planning and review workflow. Use when creating, altering, renaming, backfilling, indexing, or deleting database schema or data, especially when zero-downtime, rollback, large tables, or production safety matters.

Use cases: backend, data, productivity

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/database-migrations

What's inside

Skill name
database-migrations
Description
Database migration planning and review workflow. Use when creating, altering, renaming, backfilling, indexing, or deleting database schema or data, especially when zero-downtime, rollback, large tables, or production safety matters.
License
MIT
Instructions
23 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# Database Migrations

Use this skill when database structure or persisted data changes.

## What to Apply

- Separate schema changes from data backfills when risk or scale is meaningful.
- Prefer expand-contract migrations for renames, type changes, and destructive changes.
- Check locks, large-table behavior, default values, indexes, and rollback strategy.
- Treat deployed migrations as immutable.
- Require tests or dry runs that match the project migration tooling.

## Reference Files

- [ai-agent-standards/prompts/sample-use-cases/database-migration.md](../../ai-agent-standards/prompts/sample-use-cases/database-migration.md)
- [ai-agent-standards/engineering-practices/TESTING_STANDARDS.md](../../ai-agent-standards/engineering-practices/TESTING_STANDARDS.md)
- [ai-agent-standards/risk-management/escalation-workflow.md](../../ai-agent-standards/risk-management/escalation-workflow.md)

## Output Expectation

State the migration sequence, rollback or forward-fix plan, and verification steps before touching production data.

From JunMystery/AI-Agent-Standards, MIT.

More from JunMystery/AI-Agent-Standards

Signals

Stars
0
Forks
0
Open issues
0
Last commit (this folder)
May 25, 2026 (5 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
Repository
github.com/JunMystery/AI-Agent-Standards
First seen
Oct 24, 2026
Last checked
Oct 24, 2026
Source
GitHubgithub-graphql

More from JunMystery

Cite this page

database-migrations skill. Agent Mart. https://agentmart.dev/skills/junmystery-database-migrations (last updated 2026-10-24)