AGENT SKILL
branching-strategy
Design the branching and release model: trunk-based or GitFlow, protection rules, review policy, tracker traceability. Use when establishing Git flow, trunk-based development, or merge policies.
- License 许可
- MIT
- 最近更新
- 2026-10-02
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- branching-strategy
- group
- Repo hygiene
- description
- Design the branching and release model: trunk-based or GitFlow, protection rules, review policy, tracker traceability. Use when establishing Git flow, trunk-based development, or merge policies.
- last_reviewed
- 1788652800000
02 资源文件 2
- 其他branching-strategy.skill1.8 KB
- 参考文档evals/routing.yaml910 B
03 SKILL.md 正文
Branching Strategy
Design a branching and release process that matches how the team actually ships.
Process
- Start from release cadence. Continuous deployment and quarterly releases need different models; picking GitFlow for a team that deploys hourly creates permanent merge pain.
- Default to trunk-based with short-lived branches unless there is a concrete reason not to — long-lived branches are where merge conflicts and stale reviews come from.
- Set branch protection to match the real review capacity. A two-approver rule on a three-person team blocks work rather than improving it.
- Make the release state unambiguous. Tags, not branch names, should answer "what is in production".
- Define the hotfix path explicitly before it is needed at 2am.
- Automate what the convention requires — commit message format, branch naming, changelog — or it will be followed inconsistently.
Deliverables
- Branching model with rationale tied to release cadence
- Protection rules and required checks
- Release and tagging convention
- Hotfix runbook
Verification & Quality Checklist
- [ ] Code compiles and all automated tests and typechecks pass without new warnings.
- [ ] Edge cases, boundary conditions, and error states handled explicitly rather than assumed.
- [ ] No hardcoded secrets, credentials, or insecure defaults introduced.
- [ ] Changes are covered by a test that fails without them.
Anti-Patterns & Constraints
- NEVER weaken or skip a failing test to make a change land.
- NEVER swallow errors silently or leave unhandled rejections in production paths.
- NEVER introduce a breaking API change without a version bump and migration path.
04 同仓库更多 Skills
workflow-optimizer
Moved to workflow-mapping in skills-agents. Removed in v4.1.
★ 0
webhooks
Build webhook receivers with signature verification, idempotency, retries and dead letter queues. Use when implementing, verifying, or signing incoming/outgoing webhooks.
★ 0
webhook-handler-builder
Moved to webhooks in skills-developer. Removed in v4.1.
★ 0
voice-ai-integration-engineer
Moved to speech-pipelines in skills-developer. Removed in v4.1.
★ 0
typescript-migrator
Moved to port-code in skills-developer. Removed in v4.1.
★ 0
trigger-dev
Moved to trigger-dev in skills-agents. Removed in v4.1.
★ 0