Menu
Manage database schema migrations.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Write a structured handoff at session end. Preserves context so the next agent can resume without human briefing. Invoke before ending any feature session longer than 30 minutes.
Multi-perspective code review against project standards with P1/P2/P3 severity classification. Works in Claude Code (Agent + optional GitHub MCP) and Cursor (Task subagents + gh/git). Use when the user invokes /review, asks for a PR or diff review, or wants a standards-aligned review with severity tags.
Multi-perspective code review (P1/P2/P3) for Cursor: inline checklists plus three parallel Task subagents (perf-auditor, security-reviewer, simplicity-reviewer with combined data-integrity prompt). Use when the user invokes /review, asks for a PR review, or wants repo-standard findings with severity.
Create well-formatted git commits following conventional commit standards.
Red→green→refactor discipline for new behavior — forces a failing test before implementation and a passing test before any claim of done.
Create or manage a git worktree for isolated parallel development — lets multiple agents work in the repo simultaneously without branch collisions.
| name | migrate |
| description | Manage database schema migrations. |
Manage database schema migrations.
/db-migrate [action] [--name <migration_name>]
action: create, run, status, rollback (default: run)--name: Name for new migrationWhen this skill is invoked:
Autonomy:
Safety:
/migrate create --name add_user_profile
prd/00_technology.md for migration command{migration_create_command} --name {name}
/migrate run
{migration_status_command}
{migration_run_command}
{db_generate_command}
/migrate status
{migration_status_command}
/migrate rollback
{migration_rollback_command}
After schema changes:
# 1. Generate client (if ORM requires)
/migrate create --name describe_changes
# 2. Review generated migration
# 3. Run migration
/migrate run
# 4. Verify
/migrate status
Before deployment:
# Check pending migrations
/migrate status
# Run in production (with backup!)
/migrate run
$ /migrate create --name add_user_preferences
📋 Creating migration: add_user_preferences
Running: {migration_create_command} --name add_user_preferences
✅ Migration created: {migration_file_path}
Next steps:
1. Review the generated migration
2. Run: /migrate run
3. Regenerate client: {db_generate_command}
$ /migrate status
📋 Migration Status
Applied:
✅ 001_initial_schema (2026-01-10)
✅ 002_add_users (2026-01-12)
✅ 003_add_posts (2026-01-14)
Pending:
⏳ 004_add_user_preferences
Run '/migrate run' to apply pending migrations.