create-migration

Name: create-migration
Availability: InStock
Author: anotherben

Generate the next numbered PostgreSQL migration file with snake_case naming.

6|Updated Mar 18, 2026

Search Tags:#automation #templates #migration #sql #naming-conventions #postgres

Ready to run

npx skills add https://github.com/anotherben/claude-harness --skill create-migration-anotherben

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-migration
Source: https://github.com/anotherben/claude-harness/tree/main/skills/create-migration
Command: npx skills add https://github.com/anotherben/claude-harness --skill create-migration-anotherben

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating sequential, consistently named database migrations by hand is error-prone and slow; this skill automates generation of the next migration file, ensuring naming, structure, and conventions are followed.

Core Features & Use Cases

Automated next-number calculation by inspecting the project's migration directory.
Template-backed migration file creation with proper SQL patterns and snake_case naming.
Output of the new file path and a ready-to-review SQL skeleton for auditing and collaboration.

Quick Start

Provide a migration description to generate the next numbered migration SQL file.

Frequently Asked Questions about create-migration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I generate the next numbered PostgreSQL migration file automatically?▼

To generate the next numbered PostgreSQL migration file, provide a snake_case description and the skill calculates the next sequence number, creates the file in your migration directory, and outputs the path with a ready-to-review SQL template.

What are the project requirements for automating sequential SQL migrations?▼

Automating sequential SQL migrations requires your project to define a migration directory within the .claude/enterprise-state/stack-profile.json file, ensuring the skill can locate and calculate the next migration number accurately.

Does the generated migration SQL template follow safe database conventions?▼

Yes, the generated migration SQL template follows idempotent and safe SQL conventions, providing a standardized skeleton structure that supports safe auditing and team collaboration before database changes are applied.

How do I ensure consistent snake_case naming conventions for database migrations?▼

To ensure consistent snake_case naming conventions for database migrations, the skill applies automated template-backed file creation, enforcing precise descriptive naming based on the description you provide for each new PostgreSQL migration.

What's the best way to avoid manual errors when creating sequential database migrations?▼

The best way to avoid manual errors when creating sequential database migrations is to automate next-number calculation by inspecting the project's migration directory, ensuring naming, structure, and conventions are consistently followed.