What problem does it solve? Testing database migrations against production data is risky, and copying sensitive data into test environments creates compliance issues. This Skill guides you through choosing and creating the right Neon branch type so you can test safely without touching production. ## Core Features & Use Cases - Branch Type Selection: Decide between normal branches (full data copy for realistic migration testing) and schema-only branches (structure without sensitive rows). - CLI, MCP, and API Workflows: Create branches via the Neon CLI by default, with Neon MCP server and REST API fallbacks when the CLI is unavailable. - Branch Lifecycle Management: Reset branches from parent, set expiration dates, and define declarative branch policies in neon.ts for CI/CD pipelines. - Use Case: A developer opens a PR with a risky schema migration. The Skill creates a per-PR Neon branch with production-like data, runs the migration against it, and sets the branch to auto-expire after merge. ## Quick Start Ask the AI to create a Neon branch for testing your migration, for example: "Create a Neon branch from main so I can test my migration against production-like data."