neon-postgres-branches
Choose and create the right Neon branch type for testing and development. Use when users ask about Neon branching, migration testing with real data, isolated test environments, schema-only branch workflows for sensitive data, or branch creation via Neon CLI or Neon MCP. Triggers...
Profile →npx skills add sickn33/agentic-awesome-skills --skill neon-postgres-branches --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Neon Postgres Branching ## When to Use Use this skill when you need choose and create the right Neon branch type for testing and development. Use when users ask about Neon branching, migration testing with real data, isolated test environments, schema-only branch workflows for sensitive data, or branch creation via Neon CLI or Neon MCP. Triggers... The outcome of this skill should be a created Neon branch (or a clear, actionable next step if creation cannot proceed). Choose the correct branch type, then execute branch creation via MCP or CLI. - **Normal branch** for realistic migration and query testing with real data. - **Schema-only branch (Beta)** for sensitive data workflows where structure is needed without copying rows. ## Branch Type Decision Use this decision rule first: 1. If the user wants to test complex migrations, performance, or behavior against production-like data, choose a **normal branch**. 2. If the user needs to avoid copying sensitive data, choose a **schema-only branch**. If the request is ambiguous, ask one clarifying question: "Do you need realistic data for testing, or only schema structure because the data is sensitive?" ## Tool Selection: CLI or MCP Alw
- When to Use
- Branch Type Decision
- Tool Selection: CLI or MCP
- Selection order
- MCP branch flow
- Create a Normal Branch (Preferred for Real-Data Migration Testing)
- Steps
- Create a Schema-Only Branch (Beta, Sensitive Data)
- Beta Support Guidance (Mandatory)
- Reset from parent
- What it does
- When to recommend it
- Hard constraints and blockers
- CLI usage
neon branches create \ neon connection-string <branch-name> neon branches reset <id|name> --parent --preserve-under-name <backup-branch-name> neon branches reset <id|name> --parent --preserve-under-name <backup-branch-name> --project-id <project-id> neon set-context --project-id <project-id> npm i @neon/config
What does the neon-postgres-branches skill do?
Choose and create the right Neon branch type for testing and development. Use when users ask about Neon branching, migration testing with real data, isolated test environments, schema-only branch workflows for sensitive data, or branch creation via Neon CLI or Neon MCP. Triggers...
How do I install it?
Run `npx skills add sickn33/agentic-awesome-skills --skill neon-postgres-branches --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From sickn33/agentic-awesome-skills, a repository with 44,414 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.