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 and MCP Workflows: Create branches via the Neon CLI by default, with Neon MCP server and REST API fallbacks when the CLI is unavailable. - Reset from Parent: Refresh a drifted child branch with the parent's latest schema and data, with optional backup preservation. - Use Case: A developer opens a PR with a risky schema migration. Use this Skill to create a normal branch from main, run the migration against production-like data, verify results, and let the branch auto-expire after the PR merges. ## Quick Start Ask the AI to create a Neon branch for testing your migration, specifying whether you need realistic production data or only the schema structure.