database-branching

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.

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.

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.

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.

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.