Agent skill

Database Migration

Safely run database schema migrations. An agent skill from agulli/atlas-agents.

MITAuto-check passedDatabases

Install Database Migration

skills CLI

$ npx skills add agulli/atlas-agents --skill database-migration -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install agulli/atlas-agents database-migration --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/agulli/atlas-agents.git skills-src && mkdir -p .claude/skills && cp -r skills-src/ch09_agent_skills/skills/database-migration .claude/skills/database-migration && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "database-migration" agent skill from https://github.com/agulli/atlas-agents/tree/main/ch09_agent_skills/skills/database-migration into .claude/skills/database-migration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "database-migration", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/agulli/atlas-agents/tree/main/ch09_agent_skills/skills/database-migration

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add agulli/atlas-agents --skill database-migration -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install agulli/atlas-agents database-migration --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/agulli/atlas-agents.git skills-src && mkdir -p .agents/skills && cp -r skills-src/ch09_agent_skills/skills/database-migration .agents/skills/database-migration && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "database-migration" agent skill from https://github.com/agulli/atlas-agents/tree/main/ch09_agent_skills/skills/database-migration into .agents/skills/database-migration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "database-migration", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add agulli/atlas-agents --skill database-migration -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install agulli/atlas-agents database-migration --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/agulli/atlas-agents.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/ch09_agent_skills/skills/database-migration .cursor/skills/database-migration && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "database-migration" agent skill from https://github.com/agulli/atlas-agents/tree/main/ch09_agent_skills/skills/database-migration into .cursor/skills/database-migration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "database-migration", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/agulli/atlas-agents.git --path ch09_agent_skills/skills/database-migration

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add agulli/atlas-agents --skill database-migration -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install agulli/atlas-agents database-migration --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/agulli/atlas-agents.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/ch09_agent_skills/skills/database-migration .gemini/skills/database-migration && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "database-migration" agent skill from https://github.com/agulli/atlas-agents/tree/main/ch09_agent_skills/skills/database-migration into .gemini/skills/database-migration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "database-migration", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install agulli/atlas-agents database-migration

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add agulli/atlas-agents --skill database-migration -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/agulli/atlas-agents.git skills-src && mkdir -p .github/skills && cp -r skills-src/ch09_agent_skills/skills/database-migration .github/skills/database-migration && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "database-migration" agent skill from https://github.com/agulli/atlas-agents/tree/main/ch09_agent_skills/skills/database-migration into .github/skills/database-migration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "database-migration", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add agulli/atlas-agents --skill database-migration -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install agulli/atlas-agents database-migration --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/agulli/atlas-agents.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/ch09_agent_skills/skills/database-migration .opencode/skills/database-migration && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "database-migration" agent skill from https://github.com/agulli/atlas-agents/tree/main/ch09_agent_skills/skills/database-migration into .opencode/skills/database-migration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "database-migration", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: database-migration
GitHub stars: 578
Token cost: ~702 tokens
SKILL.md length: 317 words
Files: 1
Skills in repo: 12
Repo updated: Jul 17, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Safely run database schema migrations. An agent skill from agulli/atlas-agents.

Works in 6 steps: Identify the migration tool. Check the… → Generate the migration. → Review the generated migration file.… → …
Asked to update database schema
SKILL.md covers Clarification Gates, Process, Rationalizations and Verification
Calls python and npx

What it does

Database Migration is an agent skill from agulli/atlas-agents. Safely run database schema migrations. Use when asked to update database schema, add columns, create tables, run alembic, or apply Django migrations.

Its SKILL.md is about 700 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: Requires python 3.10+ and one of alembic, django, or prisma

It sits in Databases, covering Database migrations, Database schema design and Backend development. It works with Django and Prisma. The licence is MIT.

When your agent uses it

Asked to update database schema
Apply Django migrations

Example prompts

“/database-migration”

Requirements

Python 3
Node.js
Compatibility (from SKILL.md): Requires python 3.10+ and one of alembic, django, or prisma

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

Identify the migration tool. Check the project for
Generate the migration.
Review the generated migration file. Read the entire file. Check for
Dry run. If the tool supports it
Apply the migration only after reviewing the dry run output.
Verify. Query the database schema directly to confirm the change took effect

What it can do on your machine

Read from SKILL.md and the folder at commit 2b21998. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- python
- npx
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npx, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
Requires python 3.10+ and one of alembic, django, or prisma
From compatibility in the SKILL.md frontmatter.

Context cost

Database Migration loads about 702 tokens when it runs. Until then it costs about 42 tokens; SKILL.md has 317 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~42
When it runs · the whole SKILL.md, loaded when a task matches: ~702

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from agulli/atlas-agents at commit 2b21998, republished under its MIT licence (© agulli). 317 words, ~702 tokens.

Download SKILL.mdSave it as .claude/skills/database-migration/SKILL.md (or your agent's skills folder).

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.
compatibility: Requires python 3.10+ and one of alembic, django, or prisma
license: MIT

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"
- Django: python manage.py makemigrations
- Prisma: npx prisma migrate dev --name description
Review the generated migration file. Read the entire file. Check for:
- Columns being dropped (STOP and ask the user)
- Table renames (STOP and ask the user)
- Non-nullable columns added without defaults (this will fail on non-empty tables)
Dry run. If the tool supports it:
- Alembic: alembic upgrade head --sql (generates SQL without executing)
- Django: python manage.py sqlmigrate <app> <migration_number>
Apply the migration only after reviewing the dry run output.

Verify. Query the database schema directly to confirm the change took effect:

sql

-- PostgreSQL
SELECT column_name, data_type FROM information_schema.columns WHERE table_name = 'target_table';
-- SQLite
PRAGMA table_info(target_table);

Rationalizations

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.

Verification

Migration file was read in full before applying
No columns were dropped without explicit user approval
Database schema was queried after migration to confirm the change
"The command succeeded" is NOT accepted as sufficient evidence

Files

Just SKILL.md in ch09_agent_skills/skills/database-migration of agulli/atlas-agents.

Open the folder on GitHubat commit 2b21998

Compare with similar skills

Database Migration next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Database Migration compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Database Migration this skillagulli/atlas-agents	578	—	~702	Automated safety check: Pass	MIT	2 mo ago
Safe Database Migration Patternsaffaan-m/ECC	274k	—	~3.3k	Automated safety check: Pass	MIT	2 days ago
Database Migrationsaffaan-m/ECC	274k	4 repos	~3k	Automated safety check: Pass	MIT	2 days ago
Database Migrationsaffaan-m/ECC	274k	3 repos	~1.9k	Automated safety check: Pass	MIT	2 days ago
Database Migrationsaffaan-m/ECC	274k	1 repos	~2.4k	Automated safety check: Pass	MIT	2 days ago
Database Migrationsaffaan-m/ECC	274k	—	~335	Automated safety check: Pass	MIT	2 days ago

Similar skills

Safe Database Migration Patterns
affaan-m/ECC
Rules and examples for safe, reversible schema changes in production: zero-downtime column and index changes, large data backfills and ORM migration workflows.
274k GitHub stars~3.3k tokensUpdated 2 days ago
DatabasesAuto-check passed
Database Migrations
affaan-m/ECC
Safe, reversible database migration patterns: forward-only production changes, expand-contract zero-downtime renames, concurrent indexes, batched backfills, and per-tool workflows for PostgreSQL…
274k GitHub starsUsed in 4 repos~3k tokens
DatabasesAuto-check passed
Database Migrations
affaan-m/ECC
数据库迁移最佳实践，涵盖模式变更、数据迁移、回滚以及零停机部署，适用于PostgreSQL、MySQL及常用ORM（Prisma、Drizzle、Django、TypeORM、golang-migrate）。
274k GitHub starsUsed in 3 repos~1.9k tokens
DatabasesAuto-check passed
Database Migrations
affaan-m/ECC
Şema değişiklikleri, veri migration'ları, rollback'ler ve PostgreSQL, MySQL ve yaygın ORM'ler (Prisma, Drizzle, Django, TypeORM, golang-migrate) arasında sıfır kesinti deployment'ları için…
274k GitHub starsUsed in 1 repo~2.4k tokens
DatabasesAuto-check passed
Database Migrations
affaan-m/ECC
PostgreSQL、MySQL、一般的なORM（Prisma、Drizzle、Kysely、Django、TypeORM、golang-migrate）全体のスキーマ変更、データマイグレーション、ロールバック、ゼロダウンタイムデプロイメントのためのデータベースマイグレーションベストプラクティス。
274k GitHub stars~335 tokensUpdated 2 days ago
DatabasesAuto-check passed
DB Migrator
laolaoshiren/claude-code-skills-zh
数据库迁移助手 - Schema 对比、迁移脚本生成
877 GitHub stars~677 tokensUpdated 2 days ago
DatabasesAuto-check passed

Questions about Database Migration

What does Database Migration do?

Safely run database schema migrations. An agent skill from agulli/atlas-agents. Database Migration is an agent skill from agulli/atlas-agents. Safely run database schema migrations.

When should I use Database Migration?

Database Migration fits situations like: asked to update database schema; apply Django migrations.

How do I install Database Migration in Claude Code?

Run `npx skills add agulli/atlas-agents --skill database-migration -a claude-code`. Or copy the skill folder (ch09_agent_skills/skills/database-migration in agulli/atlas-agents) into .claude/skills/database-migration in your project. Claude Code loads it when a task matches its description.

How do I install Database Migration in Codex?

Run `npx skills add agulli/atlas-agents --skill database-migration -a codex`. Or copy the skill folder (ch09_agent_skills/skills/database-migration in agulli/atlas-agents) into .agents/skills/database-migration in your project. Codex loads it when a task matches its description.

Can I use Database Migration in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add agulli/atlas-agents --skill database-migration -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/database-migration, .gemini/skills/database-migration, .github/skills/database-migration and .opencode/skills/database-migration in your project.

What does Database Migration need to run?

Going by SKILL.md and its folder, Database Migration needs the command-line tools its instructions call (python and npx). Our summary lists: Python 3; Node.js. Compatibility (from SKILL.md): Requires python 3.10+ and one of alembic, django, or prisma.

Does Database Migration access the network?

SKILL.md contains no URLs. Its commands use npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Database Migration safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Database Migration use?

Database Migration is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Database Migration use?

About 702 tokens (SKILL.md is roughly 2.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Database Migration?

Skills that share tags, products or a category with Database Migration: Safe Database Migration Patterns (affaan-m/ECC, 274k stars), Database Migrations (affaan-m/ECC, 274k stars), Database Migrations (affaan-m/ECC, 274k stars) and Database Migrations (affaan-m/ECC, 274k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Database Migration?

agulli (a GitHub user) maintains it in agulli/atlas-agents, which has 578 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on July 17, 2026.

Source: agulli/atlas-agents on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Database Migration

Install Database Migration

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Compatibility

Context cost

Safety

SKILL.md

Clarification Gates

Process

Rationalizations

Verification

Files

Compare with similar skills

Similar skills

Safe Database Migration Patterns