CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

db:migrate

Run database migrations against the target environment. Use when applying schema changes, running pending migrations, or checking migration status. Do NOT use for seed data insertion or database backups.

Invalid
This skill can't be scored yet
Validation errors are blocking scoring. Review and fix them to unlock Quality, Impact and Security scores. See what needs fixing →
SKILL.md
Quality
Evals
Security

Database Migration Runner

Apply pending database migrations to a target environment (dev, staging, production) using Alembic.

Procedure

Step 1: Determine Target Environment

Read the environment argument. Valid values: dev, staging, production.

If production is specified, require confirmation via AskUserQuestion before proceeding:

"You are about to run migrations against PRODUCTION. This cannot be undone automatically. Continue?"

Step 2: Check Migration Status

alembic --config config/${env}.ini current
alembic --config config/${env}.ini heads

If --status flag is set, display current revision and pending migrations, then stop.

Step 3: Run Pending Migrations

alembic --config config/${env}.ini upgrade head

Report the number of migrations applied and the new current revision.

Step 4: Verify Schema

Run the schema validation script:

python scripts/verify_schema.py --env ${env}

Report any discrepancies between the expected schema and the actual database state.

If --rollback <N> is specified, roll back N migrations instead of applying:

alembic --config config/${env}.ini downgrade -${N}
Repository

LuminairPrime/git-worktrees-prime

Path

vendors/cc-skill-main/eval/runs/cc-skill-checker-eval/2026-06-01-opus/cases/case-003-mixed-quality-migration/_modified/target-skill/SKILL.md

Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.