managing-database-migrations
This skill enables Claude to manage database schema changes through version-controlled migrations. It is activated when the user requests to create, apply, or rollback database migrations. The skill supports generating timestamped migration files with both up and down migrations for PostgreSQL, MySQL, SQLite, and MongoDB. It helps in tracking schema evolution and ensuring safe database modifications. Use this skill when the user mentions "database migration", "schema change", "add column", "rollback migration", or "create migration".
- License 许可
- MIT
- 最近更新
- 2026-11-12
- Stars
- ★ 2
- Forks
- 0
01 前言 Front Matter
- name
- managing-database-migrations
- description
- This skill enables Claude to manage database schema changes through version-controlled migrations. It is activated when the user requests to create, apply, or rollback database migrations. The skill supports generating timestamped migration files with both up and down migrations for PostgreSQL, MySQL, SQLite, and MongoDB. It helps in tracking schema evolution and ensuring safe database modifications. Use this skill when the user mentions "database migration", "schema change", "add column", "rollback migration", or "create migration".
02 资源文件 3
- 资产文件assets/README.md331 B
- 参考文档references/README.md852 B
- 脚本scripts/README.md476 B
03 SKILL.md 正文
Overview
This skill empowers Claude to handle database migrations, including creating new migrations, applying changes, and rolling back previous modifications. It ensures that database schema changes are managed safely and efficiently.
How It Works
- Migration Request: The user requests a database migration task (e.g., "create a migration").
- Migration File Generation: Claude generates a timestamped migration file, including both "up" (apply changes) and "down" (rollback changes) migrations.
- Database Support: The generated migration file is compatible with PostgreSQL, MySQL, SQLite, or MongoDB.
When to Use This Skill
This skill activates when you need to:
- Create a new database migration file.
- Add a column to an existing database table.
- Rollback a previous database migration.
- Manage database schema changes.
Examples
Example 1: Adding a Column
User request: "Create a migration to add an 'email' column to the 'users' table."
The skill will:
- Generate a new migration file with timestamped name.
- Populate the 'up' migration with SQL to add the 'email' column to the 'users' table.
- Populate the 'down' migration with SQL to remove the 'email' column from the 'users' table.
Example 2: Rolling Back a Migration
User request: "Rollback the last database migration."
The skill will:
- Identify the most recently applied migration.
- Execute the 'down' migration script associated with that migration.
- Confirm the successful rollback.
Best Practices
- Idempotency: Ensure your migrations are idempotent, meaning they can be applied multiple times without unintended side effects.
- Transactions: Wrap migration steps within transactions to ensure atomicity; either all changes succeed, or none do.
- Naming Conventions: Use clear and descriptive names for your migration files (e.g.,
YYYYMMDDHHMMSS_add_email_to_users).
Integration
This skill can be used independently or in conjunction with other plugins for database management, ORM integration, and deployment automation.
04 同仓库更多 Skills
Docs Research
Use MCP Central Docs server to search, ask, and retrieve documentation (FastMCP, standards, packaging).
wrappee-drift
Read-only, single-repo audit of a repo's tool coverage against the software it wraps (its current real API/docs, not training-data memory) and against comparable/competing wrappers. Trigger when the user says "wrappee drift" followed by a repo name, "capability audit" followed by a repo name, or asks whether a repo is missing features the wrapped software or a competitor now has. Always scoped to one named repo per invocation -- never trigger this fleet-wide or unprompted; that is explicitly against the SOP. Do NOT trigger for internal fleet-standard compliance (that is drift-scan) or strategic worth/archive decisions (that is quality-check) -- this is specifically about the gap between the repo's tool list and the wrapped software's/competitors' actual current capabilities.
modules
暂无简介
mcp-standards
Use when developing MCP servers to access comprehensive standards for scaffolding, packaging, sampling, documentation, testing, error handling, monitoring, and CI/CD workflows.
webapp-cua-test
Run the pre-Tauri CUA click-through test (real browser, dev stack, OCR "Connected" wait, sidebar nav walk) for a fleet MCP server repo under D:\Dev\repos. Trigger when the user says "cua webapp test" or "webapp clickthrough" followed by a repo name, asks for an e2e click-through of a webapp, or asks whether a webapp boots and connects in a real browser. Not for the installed NSIS app (that is the nsis-build skill / cua-nsis-test) and not for DOM assertions (Playwright), and not for hunting fake data or dead buttons (fakefind).
ship
Final release gate for a fleet MCP server repo under D:\Dev\repos -- run all quality gates, build the release artifact, verify it, commit, push, and cut a GitHub release. Trigger this whenever the user says "ship it", "ship" followed by a repo name, "release" followed by a repo name, or asks to finalize and publish work that's already been done in a repo. This is the terminal step after assfix/nsis-build, not a substitute for them -- if the repo hasn't been assessed recently, say so before shipping rather than shipping blind.