database-migration

Safely run database schema migrations. Use when asked to update database schema, add columns, create tables, run alembic, or apply Django migrations.

Jump to install

Repository: agulli/atlas-agents
Last source activity: May 13, 2026 at 10:10
Detected SKILL.md language: English
Stars: 490
Forks: 103

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

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.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/agulli/atlas-agents --skill database-migration

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

api-design

Design or review REST and GraphQL API interfaces. Use when asked to design an API, review endpoint structure, define request/response schemas, or improve API ergonomics.

2026-05-13

code-review

Perform a structured security and quality audit on source code. Use when asked to review code, audit a pull request, check for vulnerabilities, or assess code quality.

2026-05-13

data-pipeline

Design, build, or debug data processing pipelines. Use when asked to process a dataset, transform data, build an ETL pipeline, schedule batch jobs, or fix data quality issues.

2026-05-13

View all from this repository

name	database-migration
description	Safely run database schema migrations. Use when asked to update database schema, add columns, create tables, run alembic, or apply Django migrations.
license	MIT
compatibility	Requires python 3.10+ and one of alembic, django, or prisma

Clarification Gates

Before executing any migration, you must have clear answers to all of the following. If any is missing or ambiguous, STOP and ask. Do not infer from filenames, branch names, or previous conversation context.

Environment: local / staging / production?
Backup confirmed: Has a database backup been taken in the last 24 hours?
Migration scope: Is this a new column/table, or does it modify/drop existing data?

An agent that guesses the environment and gets it wrong has just migrated the wrong database. Ask first.

Process

Identify the migration tool. Check the project for:
- alembic.ini → Alembic (SQLAlchemy)
- manage.py → Django migrations
- prisma/schema.prisma → Prisma If none are found, ask the user which tool to use. Do not guess.
Generate the migration.
- Alembic: alembic revision --autogenerate -m "description"

Excuse	Rebuttal
"It's just an ADD COLUMN, I'll skip the review"	Schema locks can occur even on simple additions. Always review.
"The autogenerated migration looks correct"	Autogenerate guesses. It sometimes generates DROP + CREATE instead of ALTER. Read the file.
"I'll just run it — we can roll back"	Not all migrations are reversible. Dropping a column destroys data permanently.

database-migration

Install options

Review the source files

Clarification Gates

Process

Clarification Gates

Process

Rationalizations

Verification

database-migration

Source facts

Install options

Review the source files

More from this repository

Clarification Gates

Process

More from this repository

Clarification Gates

Process

Rationalizations

Verification