database-branching

Manages Neon database branches for isolated agent workspace operations.

Updated May 6, 2026

Search Tags:#isolation #database #migrations #branching #neon #postgres #agent workspace

Ready to run

npx skills add https://github.com/UnionStreetAI/unionstreet --skill database-branching-unionstreetai

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: database-branching
Source: https://github.com/UnionStreetAI/unionstreet/tree/main/plugins/neon/skills/database-branching
Command: npx skills add https://github.com/UnionStreetAI/unionstreet --skill database-branching-unionstreetai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Agents working against shared databases risk corrupting production or staging data when running migrations or experiments. This Skill provides a safe workflow for using Neon database branches so agent work stays isolated and reversible. ## Core Features & Use Cases - Read-First Inspection: Encourages read-only inspection of the database before any write operation is proposed. - Branch-Based Isolation: Uses Neon branches to isolate agent work from the primary database. - Propose-Then-Execute Workflow: Requires proposing branch creation, migrations, and promotion steps before executing writes. - Use Case: An agent needs to test a schema migration. It inspects the current schema read-only, proposes a new Neon branch, applies the migration there, and only then suggests promotion steps. ## Quick Start Ask the agent to inspect the Neon database schema and propose a branch with the planned migration before making any changes.

Frequently Asked Questions about database-branching

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

FAQPage Schema

How do I use Neon database branches from an agent workspace?▼

Start with read-only inspection of the database, then propose branch creation, migrations, and promotion steps before executing any writes. Neon branches give each agent task an isolated copy of the database.

What is the safe workflow for running migrations with Neon branches?▼

Inspect the current schema read-only, create a Neon branch, apply and verify the migration on that branch, then propose promotion steps. Write operations should never run before the plan is reviewed.

Can agents run write operations directly on the primary Neon database?▼

No. The workflow requires read-only inspection first, then a proposal of branch creation, migrations, and promotion steps. Writes are executed only after that proposal, keeping the primary database protected.

Why use database branching instead of a shared staging database?▼

Neon branches give each agent task its own isolated database copy, avoiding conflicts between concurrent agent work on shared staging. Branches also make experiments reversible without affecting other work.

What are the limitations of this database branching skill?▼

The skill provides workflow guidance only and contains no scripts or automation, so all branch operations must be performed through Neon's own tooling. It also assumes access to a Neon project with branching enabled.