Agent skill · software engineering · sickn33
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.
Why this skill is useful
Adds specific commands and workflows for creating Neon branches that the AI wouldn't reliably generate on its own.
What it needs
Requires neon installed locally. About 7k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
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 Always support both Neon CLI and Neon MCP server. Prefer the tool the user already has installed and authenticated. MCP link: https://neon.com/docs/ai/neon-mcp-server.md CLI link: https://neon.com/docs/reference/cli-quickstart Selection order 1. Check MCP first in MCP-enabled environments: If Neon MCP tools are available and authenticated (for example, listing projects works), use MCP. 2. If MCP is unavailable or not authenticated, check CLI: Run neon --version to confirm CLI is installed. Run neon projects list to confirm auth/context. 3. If CLI is missing, direct installation via quickstart. 4. If CLI is installed but not authenticated, guide the user through neon auth (or API key auth), then continue. 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/neon-postgres-branches--32b6ba