neon-branching

Provisions Neon serverless Postgres branches per pull request.

1|1|Updated Mar 6, 2026

Search Tags:#devops #branching #neon #postgres #pr-workflow #connection-strings #neonctl

Ready to run

npx skills add https://github.com/dennisonbertram/go-agent-harness --skill neon-branching

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: neon-branching
Source: https://github.com/dennisonbertram/go-agent-harness/tree/main/skills/neon-branching
Command: npx skills add https://github.com/dennisonbertram/go-agent-harness --skill neon-branching

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Branch Neon Postgres databases to isolate changes for each pull request, enabling safe testing and previews without touching the main environment.

Core Features & Use Cases

Branch management: create, list, get, delete, reset, and set-primary branches for PR workflows.
Connection management: retrieve and use per-branch connection strings for testing and migrations.
CI/CD and preview environments: automatically provision per-PR databases to accelerate review and validation.

Quick Start

Install neonctl, authenticate, configure your project, and create a PR-named branch to start using Neon.

Frequently Asked Questions about neon-branching

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

FAQPage Schema

How do I create a Neon Postgres branch for each pull request?▼

Neon Postgres branching isolates database changes per pull request by provisioning dedicated branches for testing. This enables per-PR environments for feature testing, migrations, and rapid preview workflows without touching the main database.

What is the best way to manage database connection strings for PR preview environments?▼

Managing database connection strings for PR preview environments involves retrieving per-branch connection strings after provisioning a Neon Postgres branch. This allows isolated testing and migrations specific to each pull request without affecting the main environment.

How does database branching work for CI/CD pipelines using serverless Postgres?▼

Database branching for CI/CD pipelines using serverless Postgres works by implementing branch lifecycle operations like create, delete, and reset to isolate changes. This automatically provisions per-PR databases to accelerate review and validation workflows.

Do I need neonctl to automate Neon Postgres branch lifecycle operations?▼

You need neonctl to automate Neon Postgres branch lifecycle operations such as create, list, get, delete, reset, and set-primary. Setup guidance via neonctl and the Neon CLI configures your project to start branching for PR workflows.

Can I reset or set a primary branch when testing Postgres migrations in a PR workflow?▼

You can reset or set a primary branch when testing Postgres migrations in a PR workflow using dedicated branch lifecycle operations. Resetting reverts a branch state, while setting a primary designates the main branch for your Neon serverless Postgres project.

When should I not use Neon Postgres branching for pull request workflows?▼

You should not use Neon Postgres branching for pull request workflows if your project lacks CI/CD pipeline integration or does not require isolated per-PR database environments, as the branching lifecycle is specifically designed for feature testing and rapid preview validation.