neon-postgres-branches

Create and manage Neon Postgres branches for migration testing and isolated development environments.

Updated Sep 2, 2026
One-click install
npx skills add https://github.com/akira777777/vladfsBET --skill neon-postgres-branches-akira777777
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: neon-postgres-branches
Source: https://github.com/akira777777/vladfsBET/tree/main/.grok/skills/neon-postgres-branches
Command: npx skills add https://github.com/akira777777/vladfsBET --skill neon-postgres-branches-akira777777

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about neon-postgres-branches

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a Neon branch for testing migrations?▼

Run neon branches create with a name, parent branch, and optional expiration date, then fetch a connection string with neon connection-string. A normal branch copies production-like data so migrations are tested against realistic row shapes and volumes.

What is the difference between a normal and schema-only Neon branch?▼

A normal branch copies both schema and data from its parent, ideal for realistic migration testing. A schema-only branch copies only the structure without rows, making it suitable when sensitive production data must not be duplicated for compliance reasons.

Should I use the Neon CLI or MCP server for branching?▼

Default to the Neon CLI; verify it with neon --version and neon projects list. Switch to the Neon MCP server only when the CLI is unavailable, cannot be authenticated, or is explicitly requested, and fall back to the REST API if neither works.

How do I reset a Neon branch from its parent?▼

Run neon branches reset with the branch name, the --parent flag, and optionally --preserve-under-name to keep a backup. Only child branches can be reset, branches with children are blocked, and the reset fully replaces the child's schema and data.

Can Neon branches expire automatically in CI/CD pipelines?▼

Yes, set --expires-at when creating a branch or define a ttl in the neon.ts configuration file. Ephemeral branches with automatic expiration support branch-per-PR and branch-per-test-run patterns without accumulating storage costs.

Why can't I reset a schema-only branch from its parent?▼

Schema-only branches are independent root branches with no parent and no shared history, so reset-from-parent does not apply to them. Root branches also cannot be reset, and reset may be unavailable for up to 24 hours after a parent snapshot restore.