跳到主内容
智客 ZICQ

技能库 智客分类:运维与云 neon-postgres-branches

Neon Postgres Branches

选择和创建合适的Neon分支类型进行测试和开发. 当用户询问Neon分支时,使用真实的数据进行迁移测试,孤立的测试环境,针对敏感数据的只有子分支工作流程,从母分支重设分支,分支过期和CI/CD分支生命周期,或者通过Neon CLI或Neon MCP创建分支. 触发器包括"Neon分支","测试安全地迁移","分支生产数据","schema-只分支","重置分支","每个PR的分支"和"敏感的数据测试"等.

10047 安装量

官方网址:skills.sh

技能介绍

先看中文介绍;官方 description 原文单独保留,不改写 SKILL.md。

做什么

选择和创建用于测试和开发的正确的 Neon 分支类型

何时用

用户询问Neon分支,真实数据的迁移测试,孤立的测试环境,用于敏感数据的只有子分支工作流程,从母分支重设分支,分支过期和CI/CD分支生命周期,或通过Neon CLI或Neon MCP创建子分支. 触发器

代理如何加载

按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:Lakebase Postgres Branching、Branch Type Decision、Tool Selection: CLI or MCP、Selection order、MCP branch flow、Create a Normal Branch (Preferred for Real-Data Migration Testing)。 其中含规范建议的小节:分步指令。

文件分析

文件分析:这是一份仅含 SKILL.md 的指令型技能,代理激活后整份正文进入上下文。

官方 description(原文)

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, resetting a branch from its parent, branch expiration and CI/CD branch lifecycles, or branch creation via Neon CLI or Neon MCP. Triggers include "Neon branch", "test migrations safely", "branch production data", "schema-only branch", "reset branch", "branch per PR" and "sensitive data testing".

Lakebase Postgres BranchingBranch Type DecisionTool Selection: CLI or MCPSelection orderMCP branch flowCreate a Normal Branch (Preferred for Real-Data Migration Testing)StepsCreate a Schema-Only Branch (Beta, Sensitive Data)StepsBeta Support Guidance (Mandatory)Reset from ParentWhat it does

来源分类:skills.sh agent-skill

SKILL.md 与 Agent 调用

官方规范 ↗
name
neon-postgres-branches
description
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, resetting a branch from its parent, branch expiration and CI/CD branch lifecycles, or branch creation via Neon CLI or Neon MCP. Triggers include "Neon branch", "test migrations safely", "branch production data", "schema-only branch", "reset branch", "branch per PR" and "sensitive data testing".
  1. 发现技能客户端向 Agent 提供名称与描述目录。
  2. 匹配与调用用户指定或任务匹配后,载入 SKILL.md 指令。
  3. 按需加载按步骤读取参考文档、使用脚本与素材。

具体调用语法与可用工具以目标 Agent 客户端为准。 查看调用机制说明 ↗

安装这个技能

Skills CLI ↗

先选择目标 Agent 和安装范围,保留技能包的附属文件,安装后检查客户端能否发现该技能。

交给 Agent 安装

复制安装指令给支持 Agent Skills 的代理,确认其中的目标目录与客户端匹配。

把 Agent Skill「neon-postgres-branches」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-cdfe00733d77dd8c-%E9%9C%93%E8%99%B9%E7%81%AF%E5%88%86%E8%A1%8C.html
请存为 .cursor/skills/neon-postgres-branches/SKILL.md 或 .claude/skills/neon-postgres-branches/SKILL.md,frontmatter 的 name 与 description 保持原样,不要改写。

GitHub 完整包 ↗

终端安装 · Skills CLI

需要 Node.js 与 npx。先查看仓库技能列表,确认实际名称。

npx skills add 'https://github.com/neondatabase/agent-skills' --list

npx skills add 'https://github.com/neondatabase/agent-skills' --skill 'neon-postgres-branches'

CLI 会交互选择目标 Agent,默认安装到项目;用户级安装使用 -g。先通过查看命令核对仓库内容,再用 npx skills list 检查已安装技能。

阅读排版
--- name: neon-postgres-branches description: >- 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, resetting a branch from its parent, branch expiration and CI/CD branch lifecycles, or branch creation via Neon CLI or Neon MCP. Triggers include "Neon branch", "test migrations safely", "branch production data", "schema-only branch", "reset branch", "branch per PR" and "sensitive data testing". metadata: parent: neon source: https://github.com/neondatabase/agent-skills/tree/main/skills/neon-postgres-branches --- **FIRST**: Use the parent `neon` skill for a Neon overview, getting started with Neon, Neon development best practices, and more. If the `neon` skill is not installed, fetch it from https://neon.com/docs/ai/skills/neon/SKILL.md or install it with: ```bash neon skills -s neon -y ``` # Lakebase Postgres Branching **Outcome:** a created Neon branch — or a clear, actionable next step if creation cannot proceed. Choose the correct branch type, then execute branch creation with the CLI (or MCP where the CLI isn't usable). - **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 Support both the Neon CLI and the Neon MCP server, but **default to the CLI**. Use MCP only when the CLI is unavailable or blocked in your environment, cannot be authenticated, or the user explicitly asks for MCP. - CLI link: https://neon.com/docs/cli/quickstart.md - MCP link: https://neon.com/docs/ai/neon-mcp-server.md ### Selection order 1. Check the CLI first: - Run `neon --version` to confirm the CLI is installed. - Run `neon projects list` to confirm auth/context. 2. If the CLI is missing, direct installation via quickstart. 3. If the CLI is installed but not authenticated, guide the user through `neon auth` (or API key auth), then continue. 4. Switch to MCP when the CLI cannot be used — no CLI access in the environment, execution blocked, or authentication not possible — or when the user explicitly asks for MCP. Confirm Neon MCP tools are available and authenticated (for example, listing projects works), then follow the MCP branch flow below. 5. If neither path is successful, use the Neon REST API: - https://neon.com/docs/guides/branching-neon-api.md ### MCP branch flow 1. Choose normal vs schema-only based on data sensitivity and migration-testing goals. 2. Use branch tools (for example, `create_branch`) to create the branch. 3. Validate with read tools (for example, `describe_branch`). 4. For migration workflows, prefer branch-based migration flows before applying to main. ## Create a Normal Branch (Preferred for Real-Data Migration Testing) Use this when the user needs realistic testing conditions. Real production-like data can expose edge cases your seed or data migration scripts miss, which helps catch migration issues before going live. Link: https://neon.com/docs/introduction/branching.md ### Steps 1. Settle the tool path first (see [Selection order](#selection-order)): verify the CLI with `neon --version`, and fall back to MCP only if the CLI isn't usable. 2. Ensure project context is set (`neon set-context --project-id `) or include `--project-id` on commands. 3. Create the branch: ```bash neon branches create \ --name \ --parent \ --expires-at 2026-12-15T18:02:16Z ``` 4. Optionally fetch a connection string for the new branch: ```bash neon connection-string ``` ## Create a Schema-Only Branch (Beta, Sensitive Data) Use this when users must not copy production rows into the test branch. Link: https://neon.com/docs/guides/branching-schema-only.md ### Steps 1. Settle the tool path first (see [Selection order](#selection-order)): verify the CLI with `neon --version`, and fall back to MCP only if the CLI isn't usable. 2. Create the schema-only branch: ```bash neon branches create \ --name \ --parent \ --schema-only \ --expires-at 2026-12-15T18:02:16Z ``` If multiple projects exist, include `--project-id`: ```bash neon branches create \ --name \ --parent \ --schema-only \ --project-id \ --expires-at 2026-12-15T18:02:16Z ``` ### Beta Support Guidance (Mandatory) Schema-only branching is in Beta. If users report unexpected behavior, errors, or missing capabilities: 1. Ask them to share feedback in the Neon Console: - https://console.neon.tech/app/projects?modal=feedback 2. Recommend opening a support conversation in the Neon Discord: - https://discord.gg/92vNTzKDGp ## Reset from Parent Use this when a child branch has drifted and the user wants a clean refresh from the parent branch's latest schema and data. Link: https://neon.com/docs/guides/reset-from-parent.md ### What it does - Fully replaces the child branch schema and data with the parent's latest state. - Does not merge; local changes on the child branch are lost. - Keeps the same connection details, but active connections are briefly interrupted during reset. ### When to recommend it - Development or staging branch is too far behind production. - User wants to start a new feature from a clean parent-aligned state. - Team wants to refresh staging from production for consistent testing baselines. ### Hard constraints and blockers - Only child branches can be reset (root branches and schema-only root branches cannot be reset from parent). - If the target branch has children, reset is blocked until those child branches are removed. - After a parent branch is restored from snapshot, reset-from-parent may be unavailable for up to 24 hours. - Reset-from-parent always uses the current parent state; use Instant restore for point-in-time recovery needs. ### CLI usage ```bash neon branches reset --parent --preserve-under-name ``` If project context is not already set, include the project ID: ```bash neon branches reset --parent --preserve-under-name --project-id ``` `--preserve-under-name` keeps the pre-reset state as a backup branch for rollback, but adds one extra branch to clean up later. Optional context setup to avoid repeating `--project-id`: ```bash neon set-context --project-id ``` ### Console and API usage - **Console:** Open the target child branch, then select **Reset from parent** from **Actions**. - **API:** Use the restore endpoint for the branch and set `source_branch_id` to the parent branch ID. ## Notes and Caveats - Schema-only branches are for structure-only cloning and sensitive/compliant data controls. - Schema-only branches are independent root branches (no parent branch and no shared history), so reset-from-parent does not apply. - For migration testing that depends on real-world row shapes, volumes, and edge cases, prefer normal branches. - Root branch allowances and per-branch storage limits can cap how many schema-only branches users can create. - If a user is unsure, default recommendation is: - **Normal branch** for migration validation. - **Schema-only branch** for compliance and privacy constraints. ## Useful Workflow Patterns If the user asks for process recommendations (not just a single command), suggest these: - **One branch per PR:** Create branch when PR opens, delete when merged/closed, keep migration tests isolated. - **One branch per test run:** Create branch at pipeline start, run migrations/tests, delete at end for deterministic CI. - **One branch per developer:** Isolated dev environments with production-like shape; avoid team collisions on shared test data. - **PII-aware branching:** If production has sensitive data, derive dev/PR branches from an anonymized branch or use schema-only branches. - **Ephemeral lifecycle hygiene:** Set branch expiration and automate cleanup so old branches do not accumulate avoidable storage/history cost. ### Post-creation environment update prompt After branch creation, ask whether the user wants to update local environment credentials to point at the new branch. - Ask: "Do you want me to update your `.env` `DATABASE_URL` to this new branch connection string?" - If yes, write the new branch connection string to the requested env file/key. - If no, leave credentials unchanged and share the connection string for manual use. - Never overwrite an existing env key without explicit confirmation. ## Neon Infrastructure as Code (`neon.ts`) Beyond creating branches imperatively (CLI / MCP / API above), you can **program what configuration new branches receive** declaratively in `neon.ts` — Neon's infrastructure-as-code file (see the `neon` skill for the full reference). The `branch` property is a function of the branch being evaluated that returns its settings, so every branch born from your project gets a consistent lifecycle and compute profile without per-branch flags. ```bash npm i @neon/config ``` ```typescript // neon.ts import { defineConfig } from "@neon/config/v1"; export default defineConfig({ branch: (branch) => { if (branch.exists) return {}; // never reconcile existing branches if (branch.isDefault) return { protected: true }; if (branch.name.startsWith("preview/") || branch.name.startsWith("dev")) { return { parent: "main", ttl: "7d", // ephemeral: auto-expire 7 days after creation (max 30d) postgres: { computeSettings: { autoscalingLimitMinCu: 0.25, // scale to zero autoscalingLimitMaxCu: 1, // keep throwaway branches cheap suspendTimeout: "5m", }, }, }; } return {}; }, }); ``` The closure receives a read-only descriptor of the target branch — `name`, `exists`, `isDefault`, `parentId`, and more — and returns the tuning to apply: `parent`, `ttl` (auto-expiry), `protected`, and `postgres.computeSettings`. This is the declarative complement to the **Ephemeral lifecycle hygiene** and per-PR / per-test patterns above: instead of remembering `--expires-at` on every `neon branches create`, the TTL and compute profile live in version control and apply to every matching branch. Because `neon checkout` applies this policy when it **creates** a branch, a fresh `preview/*` or `dev-*` branch comes up already expiring and scaled-to-zero. Checking out an _existing_ branch doesn't reconcile it — run `neon deploy` (alias for `neon config apply`) to apply changes to a branch that already exists. ## Branching in CI/CD Common CI/CD use cases for Neon branches: - **Per-PR preview deployments:** Branch on PR open, deploy the preview against it, delete on close. Each PR gets an isolated database branch. Injecting the branch's `DATABASE_URL` into the deployed app is hosting-provider-specific — see [preview-branches-with-cloudflare](https://github.com/neondatabase/preview-branches-with-cloudflare), [preview-branches-with-vercel](https://github.com/neondatabase/preview-branches-with-vercel), or [preview-branches-with-fly](https://github.com/neondatabase/preview-branches-with-fly) for tested patterns. - **Migration testing in CI:** Run risky schema changes against a branch with production-like data before merge. - **Schema diff visibility:** Use the [schema-diff GitHub Action](https://github.com/marketplace/actions/neon-schema-diff-github-action) to auto-comment a DB-layer diff on the PR. ## Examples ### Example 1: Migration testing with realistic data **User input:** "I need to test a risky migration against production-like data." **Agent output shape:** 1. Recommend a normal branch and explain why. 2. Share docs link: https://neon.com/docs/introduction/branching 3. Check the tool path first (CLI with `neon --version`; MCP only if the CLI isn't usable). 4. Provide commands: - `neon branches create --name migration-test --parent main --expires-at 2026-12-15T18:02:16Z` - `neon connection-string migration-test` ### Example 2: Sensitive data development workflow **User input:** "We cannot copy production data because of compliance." **Agent output shape:** 1. Recommend schema-only branch and explain why. 2. Share docs link: https://neon.com/docs/guides/branching-schema-only 3. Check the tool path first (CLI with `neon --version`; MCP only if the CLI isn't usable). 4. Provide command: - `neon branches create --name compliance-dev --parent main --schema-only --project-id --expires-at 2026-12-15T18:02:16Z` 5. Mention Beta support path: - https://console.neon.tech/app/projects?modal=feedback - https://discord.gg/92vNTzKDGp ## Further Reading - https://neon.com/docs/guides/branch-expiration.md - https://neon.com/docs/guides/neon-github-integration.md - https://neon.com/docs/ai/neon-mcp-server.md - https://neon.com/branching

相关技能

运维与云

Docker Essentials

用于容器管理,图像操作,调试的基本道克命令和工作流程.

运维与云

Find Skills

从开放的代理技能生态系统中发现并安装技能. 使用时:(1)用户问"我如何做X",X可能拥有现有技能,(2)用户说"为X找到技能"或"是否为X有技能",(3)用户问"你能否做X",X是专门能力,(4)用户想扩展代理能力,(5)用户想搜索工具,模板,或工作流程,(6)用户提到他们希望…

运维与云

Microsoft Foundry

构建,部署,评价,优化,微调,管理微软创始代理,模型,资源最终结束. 用法:铸造、azd ai代理、azd 提供/部署、托管代理脚手架/开发/运行/部署/拖放、即时代理创建、创建代理、更新代理、添加代理工具、援引代理、代理.yaml、评估代理、批量活化、连续活化、持续监测、代理C…

运维与云

Azure Deploy

执行已有.azure/部署计划.md和基础设施文件的ALREADY-PREPARED应用程序的Azure部署。 当用户向 CREATE 请求新应用程序时, 请不要使用此技能 。 这种技能运行了 azd上行, azd 部署, trarraform 应用, 和 az 部署命令带有内置…