AGENT SKILL

standard-git-branching

Company Git branching and release standard (GitHub Flow with Conventional Commits). Use when creating or naming feat/fix/chore/spec branches, choosing a merge target, writing a squash-merge title, cutting a release/* branch, tagging, maintaining lts/* lines, or cherry-picking fixes.

License 许可
MIT
最近更新
2026-11-11
Stars
★ 0
Forks
0

01 前言 Front Matter

name
standard-git-branching
description
Company Git branching and release standard (GitHub Flow with Conventional Commits). Use when creating or naming feat/fix/chore/spec branches, choosing a merge target, writing a squash-merge title, cutting a release/* branch, tagging, maintaining lts/* lines, or cherry-picking fixes.

03 SKILL.md 正文

standard-git-branching

<!-- generated by standards.py from projectious-work/standards; do not edit -->

Binding company standard. The rules below are the summary; the linked file is authoritative. Read only the section the task needs.

Git branching and release standard

GitHub Flow, Conventional Commits, 50/72 Rule: feat/, fix/, chore/, spec/ from main as [<issue>-]<slug>; unclear target: stop. Squash-merge after explicit owner approval; title type matches the prefix. release/vX.Y.Z holds only chore(release): vX.Y.Z; tag the squash commit. Specs: tag spec/<slug>/vN. lts/vN: names lts<N>-…; fix main first, then git cherry-pick -x. Never develop on release/* or bypass protection.

Full standard: .standards/git-branching-and-releases.md. Sections:

  • Purpose and scope
  • Branches
  • Normal flow
  • Specifications
  • Releases and tags
  • Long-term support
  • Approval and merge authority
  • Protection and audit requirements
  • Migration from version lines
  • Authoritative references

04 同仓库更多 Skills