What problem does it solve? Testing database migrations against production data is risky, and copying sensitive data into test environments creates compliance problems. This Skill guides you through choosing and creating the right Neon branch type so you can validate schema changes 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) based on your data sensitivity needs. - 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 branch preservation. - CI/CD Patterns: Apply branch-per-PR, branch-per-test-run, and ephemeral lifecycle patterns with expiration and declarative neon.ts configuration. - Use Case: You need to test a risky migration before merging. Create a normal branch from main with an expiration date, run your migration against production-like data, and let the branch auto-expire after validation. ## 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.