How do I install the Create database migration skill?

Run npx skillmds add tryghost/create-database-migration in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Create database migration safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Create database migration?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Create database migration free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Create database migration?

TryGhost (@tryghost) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Create database migration by tryghost

Name: Create database migration
Rating: 4.2 (5 reviews)
Author: TryGhost

Create database migration

Create a database migration to add a table, add columns to an existing table, add a setting, or otherwise change the schema of Ghost's MySQL database. Use this skill whenever the task involves modifying Ghost's database schema — including adding, removing, or renaming columns or tables, adding new settings, creating indexes, updating data, or any change that requires a migration file in ghost/core. Also use when the user references schema.js, knex-migrator, the migrations directory, or asks to "add a field" or "add a column" to any Ghost model/table. Even if the user frames it as a feature or Linear issue, if the implementation requires a schema change, this skill applies.

TryGhost e6bd516 3 files · 5.8 KB Updated Sep 10, 2026

File contents

Create Database Migration

Read the canonical human guidance in docs/practices/database-migrations.md before making a migration. This skill is the executable checklist that accompanies it.

Instructions

Create a new, empty migration file: cd ghost/core && pnpm migrate:create <kebab-case-slug>. IMPORTANT: do not create the migration file manually; always use this script to create the initial empty migration file. The slug must be kebab-case (e.g. add-column-to-posts).
The above command will create a new directory in ghost/core/core/server/data/migrations/versions if needed, create the empty migration file with the appropriate name, and bump the core and admin package versions to RC if this is the first migration after a release.
Update the migration file with the changes you want to make in the database, following the existing patterns in the codebase. Where appropriate, prefer to use the utility functions in ghost/core/core/server/data/migrations/utils/*.
Update the schema definition file in ghost/core/core/server/data/schema/schema.js, and make sure it aligns with the latest changes from the migration.
Test the migration manually: cd ghost/core && pnpm knex-migrator migrate --v {version directory} --force
Roll the migration back to test down(): cd ghost/core && pnpm knex-migrator rollback --v {previous version} --force, then migrate forward again.
Run the migration integration test, which covers initialization, rollback, forward migration, and idempotency: cd ghost/core && pnpm test:single test/integration/migrations/migration.test.js. Migrations must pass the database-backed suites against both MySQL and SQLite.
If adding or dropping a table, update ghost/core/core/server/data/exporter/table-lists.js as appropriate. The consistency assertion in ghost/core/test/unit/server/data/exporter/index.test.js checks that every schema table is classified in the exporter lists.
Run the focused exporter unit test when the table lists change: cd ghost/core && pnpm test:single test/unit/server/data/exporter/index.test.js.
Run the schema integrity test, and update the hash: cd ghost/core && pnpm test:single test/unit/server/data/schema/integrity.test.js
Run unit tests in Ghost core, and iterate until they pass: cd ghost/core && pnpm test:unit

Examples

See examples.md for example migrations.

Rules

See rules.md for rules that should always be followed when creating database migrations.

---name: create-database-migrationdescription: Create a database migration to add a table, add columns to an existing table, add a setting, or otherwise change the schema of Ghost's MySQL database. Use this skill whenever the task involves modifying Ghost's database schema — including adding, removing, or renaming columns or tables, adding new settings, creating indexes, updating data, or any change that requires a migration file in ghost/core. Also use when the user references schema.js, knex-migrator, the migrations directory, or asks to "add a field" or "add a column" to any Ghost model/table. Even if the user frames it as a feature or Linear issue, if the implementation requires a schema change, this skill applies.---# Create Database MigrationRead the canonical human guidance in[`docs/practices/database-migrations.md`](../../../docs/practices/database-migrations.md)before making a migration. This skill is the executable checklist thataccompanies it.## Instructions1. Create a new, empty migration file: `cd ghost/core && pnpm migrate:create <kebab-case-slug>`. IMPORTANT: do not create the migration file manually; always use this script to create the initial empty migration file. The slug must be kebab-case (e.g. `add-column-to-posts`).2. The above command will create a new directory in `ghost/core/core/server/data/migrations/versions` if needed, create the empty migration file with the appropriate name, and bump the core and admin package versions to RC if this is the first migration after a release.3. Update the migration file with the changes you want to make in the database, following the existing patterns in the codebase. Where appropriate, prefer to use the utility functions in `ghost/core/core/server/data/migrations/utils/*`.4. Update the schema definition file in `ghost/core/core/server/data/schema/schema.js`, and make sure it aligns with the latest changes from the migration.5. Test the migration manually: `cd ghost/core && pnpm knex-migrator migrate --v {version directory} --force`6. Roll the migration back to test `down()`: `cd ghost/core && pnpm knex-migrator rollback --v {previous version} --force`, then migrate forward again.7. Run the migration integration test, which covers initialization, rollback, forward migration, and idempotency: `cd ghost/core && pnpm test:single test/integration/migrations/migration.test.js`. Migrations must pass the database-backed suites against both MySQL and SQLite.8. If adding or dropping a table, update `ghost/core/core/server/data/exporter/table-lists.js` as appropriate. The consistency assertion in `ghost/core/test/unit/server/data/exporter/index.test.js` checks that every schema table is classified in the exporter lists.9. Run the focused exporter unit test when the table lists change: `cd ghost/core && pnpm test:single test/unit/server/data/exporter/index.test.js`.10. Run the schema integrity test, and update the hash: `cd ghost/core && pnpm test:single test/unit/server/data/schema/integrity.test.js`11. Run unit tests in Ghost core, and iterate until they pass: `cd ghost/core && pnpm test:unit`## ExamplesSee [examples.md](examples.md) for example migrations.## RulesSee [rules.md](rules.md) for rules that should always be followed when creating database migrations.

Frequently asked questions