AutoGineer
Generated banner for Neon Migration Specialist
Generated logo for Neon Migration Specialist

Neon Migration Specialist

GitHubOfficialFirst committed by aaronpowellDistributed by GitHub

  • Custom agent
  • Workflow
  • Cloud and DevOps
  • MIT
  • No issues found
Download ZIP

From the author

Safe Postgres migrations with zero-downtime using Neon's branching workflow. Test schema changes in isolated database branches, validate thoroughly, then apply to production—all automated with support for Prisma, Drizzle, or your favorite ORM.
— the description by aaronpowell

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

The Neon Migration Specialist is an agentic workflow designed to facilitate safe database schema changes for Neon Serverless Postgres. By leveraging Neon's branching capabilities, the agent creates isolated, temporary database environments to test migrations before they are applied to production. It integrates with existing ORM systems like Prisma or Drizzle and ensures that all schema modifications are validated in a sandbox, preventing production downtime and data loss.

What it does

  • Creates isolated Neon database branches for testing schema changes
  • Executes migrations against temporary branches to validate compatibility
  • Integrates with existing ORM migration systems like Prisma or Drizzle
  • Generates migration SQL using migra as a fallback when no ORM is present
  • Ensures clean-up by deleting temporary database branches after validation
  • Prepares migration files for PR submission to the main repository

When to use it

  • When you need to apply schema changes to a Neon Postgres database without risking production downtime
  • When you want to automate the validation of database migrations in an isolated environment
  • When you are using an ORM and need a structured way to test migrations before committing them
  • When you need to generate migration SQL by comparing schema states

Advantages

  • Eliminates production risk by testing migrations on isolated database branches
  • Supports zero-downtime deployment strategies
  • Works seamlessly with popular ORMs like Prisma and Drizzle
  • Automates the lifecycle of temporary test environments
  • Ensures consistent migration practices across development workflows

Usage examples

“I need to add a new column to my users table in my Neon project. Can you help me test this migration?”
The agent will create a temporary Neon database branch, run the migration against it, verify the schema change, and then provide the migration file for your PR.
“My project uses Drizzle. How can I safely apply my latest schema changes to my Neon database?”
The agent will detect the Drizzle setup, create a test branch, run the Drizzle migration command against that branch, and confirm success before advising you to merge.

Install

  1. Download the custom agent as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/github/neon-migration-specialist/download

  2. Extract the agent file into .github/agents, then commit it:

    mkdir -p .github/agents && unzip -j neon-migration-specialist.zip 'neon-migration-specialist/neon-migration-specialist.agent.md' -d .github/agents

  3. Keep the LICENSE and ATTRIBUTION.md files from the ZIP with your copy.

Documentation by aaronpowell

Neon Database Migration Specialist

You are a database migration specialist for Neon Serverless Postgres. You perform safe, reversible schema changes using Neon's branching workflow.

Prerequisites

The user must provide:

Reference Neon branching documentation: https://neon.com/llms/manage-branches.txt

Use the Neon API directly. Do not use neonctl.

Core Workflow

  1. Create a test Neon database branch from main with a 4-hour TTL using expires_at in RFC 3339 format (e.g., 2025-07-15T18:02:16Z)

  2. Run migrations on the test Neon database branch using the branch-specific connection string to validate they work

  3. Validate the changes thoroughly

  4. Delete the test Neon database branch after validation

  5. Create migration files and open a PR—let the user or CI/CD apply the migration to the main Neon database branch

CRITICAL: DO NOT RUN MIGRATIONS ON THE MAIN NEON DATABASE BRANCH. Only test on Neon database branches. The migration should be committed to the git repository for the user or CI/CD to execute on main.

Always distinguish between Neon database branches and git branches. Never refer to either as just "branch" without the qualifier.

Migration Tools Priority

  1. Prefer existing ORMs: Use the project's migration system if present (Prisma, Drizzle, SQLAlchemy, Django ORM, Active Record, Hibernate, etc.)

  2. Use migra as fallback: Only if no migration system exists

    • Capture existing schema from main Neon database branch (skip if project has no schema yet)

    • Generate migration SQL by comparing against main Neon database branch

    • DO NOT install migra if a migration system already exists

File Management

Do not create new markdown files. Only modify existing files when necessary and relevant to the migration. It is perfectly acceptable to complete a migration without adding or modifying any markdown files.

Key Principles

  • Neon is Postgres—assume Postgres compatibility throughout

  • Test all migrations on Neon database branches before applying to main

  • Clean up test Neon database branches after completion

  • Prioritize zero-downtime strategies

Files

Requirements and compatibility

Written for: GitHub Copilot

Works with: GitHub Copilot

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Needs an API key

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

First committed by
GitHub avatar of aaronpowellaaronpowell
Publisher
GitHub (Official)
Distributed by
GitHub
Source
github/awesome-copilot · agents/neon-migration-specialist.agent.md · commit 797337f
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced
Contributors
aaronpowell

AutoGineer is not affiliated with or endorsed by aaronpowell or GitHub.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download neon-migration-specialist.zip