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 (real data 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 child branches from parent, set branch expiration, and define declarative branch policies in neon.ts for CI/CD pipelines. - Use Case: Before merging a risky schema migration, create a normal branch from main with production-like data, run the migration against it, and delete the branch when the PR closes. ## Quick Start Ask the AI to create a Neon branch for testing your migration, and it will verify the CLI, pick the right branch type, and run the creation command.