neon-postgres-branches: a Claude Code skill by Neon
Official
For teams on Neon Postgres who want to test migrations on a copy of production. Skip it if your database isn't on Neon or you never branch data for tests.
Before you install: If the parent neon skill is missing, it tells Claude to install it with `neon skills -s neon -y` or fetch it from neon.com, which adds more instructions without a review step.
- Score
- 77of 100
- Rank
- #92of 239
- Installs
- 37.3Kon skills.sh
- Security
- Clear 3 scanners
- Updated
- 2026
- Context
- ~135tokens always
Install
npx skills add https://github.com/neondatabase/agent-skills --skill neon-postgres-branches Run it in your terminal. View the source
Using the Claude app rather than Claude Code? You can add a skill there too. How to add it in the app
What does neon-postgres-branches do?
neon-postgres-branches is a skill that picks and creates the right Neon database branch for a testing job. A normal branch copies real data for migration and query tests. A schema-only branch, still in Beta, copies structure without rows when the data is sensitive. It checks neon --version and neon projects list first, then falls back to Neon MCP and finally the REST API. It runs neon branches create with an expiry date, can reset a child branch from its parent while keeping a backup, and offers to put the new connection string in .env only after asking. It also covers per-PR branches and neon.ts policies.
When should you use neon-postgres-branches?
Use it when
- You want to test a risky migration on production-like data
- Compliance rules stop you from copying real rows
- You want a fresh database branch for each pull request
Skip it when
- Your database isn't hosted on Neon
- You only need a local throwaway database
What it needs and what it can touch
You need
- A Neon account
- The Neon CLI, or the Neon MCP server
What it can do
- Runs shell commands (neon CLI)
- Creates and resets branches in your Neon project
- Edits your .env DATABASE_URL after you confirm
From reading its instructions, not from running it.
Why it scores 77
Strongest on upkeep (100 of 100), weakest on adoption (41).
Is neon-postgres-branches safe to install?
Every scanner that checked it passed it. Scanners often miss what other scanners catch, and a skill can change after a scan. Read its source before you install it.
| Scanner | Result | Date |
|---|---|---|
| Gen Agent Trust Hub | Passed | Sep 24, 2026 |
| Socket | Passed | Sep 24, 2026 |
| Snyk | Low risk | Sep 24, 2026 |
Details
- Installs
- 37,325
- Repository stars
- 112
- Last repository change
- Tokens always loaded
- about 135
- Tokens when used
- about 3,233
- License
- Apache-2.0
- Data confidence
- High
Did it do the job for you?
Alternatives to neon-postgres-branches
All skills for this job-
Get neonneon
For developers putting an app's database, login, files or functions on Neon who want Claude to drive the neon CLI.
-
Get PrismaPrisma
For TypeScript developers on Prisma ORM who want correct queries, CLI commands and database setup.
-
Get supabase-postgres-best-practicessupabase-postgres-best-practices
For developers writing SQL, schemas or row level security policies on any Postgres database.
-
Get convexconvex
For developers building on Convex or wanting a TypeScript backend with a realtime database.