菜单
Use when initializing or checking Git Flow, creating feature/bugfix/release/hotfix branches, or managing branch lifecycle in SSPU-AllinOne. Covers gitflow vs git flow command detection, branch targets, manual branch classes, and cross-platform setup.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | git-flow |
| description | Use when initializing or checking Git Flow, creating feature/bugfix/release/hotfix branches, or managing branch lifecycle in SSPU-AllinOne. Covers gitflow vs git flow command detection, branch targets, manual branch classes, and cross-platform setup. |
Use this skill for SSPU-AllinOne branch lifecycle work.
gitflow or git flow.maindevelopfeature/bugfix/release/hotfix/support/vDo not replace the Bugfix branch prefix with fix/. The branch prefix is bugfix/; the commit and PR type remains fix(scope): 中文摘要.
Try both command surfaces and use the one that works in the current shell:
gitflow --version
git flow version
git config --get-regexp '^gitflow\.'
Use the repo helper when available:
pwsh ./scripts/gitflow/check_config.ps1
bash ./scripts/gitflow/check_config.sh
Initialize only on a fresh clone or a clone without Git Flow config:
<git-flow> init -d
winget install Kubis1982.GitFlow commonly provides gitflow; some Git extension installs provide git flow.brew install git-flow commonly provides git flow.sudo apt-get install git-flow; command surface depends on package/version.gitflow / git-flow) or the approved package source.sudo pacman -S gitflow-avh or the approved package; command surface depends on package/version.After installation, restart the terminal if neither command surface is found.
| Work | Branch | Target |
|---|---|---|
| Feature | feature/<topic> | develop |
| Bug fix | bugfix/<topic> | develop |
| Docs | docs/<topic> | develop |
| Chore | chore/<topic> | develop |
| Refactor | refactor/<topic> | develop |
| Test | test/<topic> | develop |
| CI / governance | ci/<topic> | develop |
| Dependencies | deps/<topic> | develop |
| Pre-release | `release/vX.X.X-alpha | beta |
| Stable / lts / hotfix release prep | `release/vX.X.X[-lts | -hotfix]` |
| Emergency integration | hotfix/<topic-or-version> | develop; publish through the release flow |
Except for develop -> main release promotion or default-branch sync, PRs target develop.
Use these when the local Git Flow tool supports the branch class. Replace <git-flow> with gitflow or git flow:
git checkout develop
git pull --ff-only origin develop
<git-flow> feature start <topic-kebab-case>
<git-flow> bugfix start <topic-kebab-case>
<git-flow> release start vX.X.X[-channel]
<git-flow> hotfix start <topic-or-version>
Finish commands merge locally and delete branches. Prefer PR-based finishing unless the user explicitly asks for local Git Flow finish:
<git-flow> feature finish <name>
<git-flow> bugfix finish <name>
<git-flow> release finish <version>
<git-flow> hotfix finish <name>
The installed Git Flow command does not provide docs start, chore start, ci start, or similar subcommands. Create those branches manually:
git checkout develop
git pull --ff-only origin develop
git checkout -b docs/<topic-kebab-case>
git checkout -b chore/<topic-kebab-case>
git checkout -b refactor/<topic-kebab-case>
git checkout -b test/<topic-kebab-case>
git checkout -b ci/<topic-kebab-case>
git checkout -b deps/<topic-kebab-case>
[personal-prefix/]<type>/<topic-kebab-case>qintsg/feature/wechat-subscription.feature/wechat-subscription, bugfix/scorecard-243-sha, docs/release-governance, ci/github-actions-upgrade, deps/flutter-upgrade.git status --short --branch
git branch --show-current
Confirm the branch is not develop or main, has the expected prefix, and targets develop unless it is the explicit develop -> main promotion.
Use when checking out a new branch to work on an issue in SSPU-AllinOne. Covers the issue-to-branch flow, Git Flow bugfix naming, manual branch classes, and ready-to-edit verification.
Use when writing git commit messages in SSPU-AllinOne. Covers required title format, allowed types, branch-to-type mapping, Chinese summaries, issue references, and Lore trailers.
Use when creating or editing GitHub issues in SSPU-AllinOne. Covers issue templates, required fields, labels, sensitive-data hygiene, acceptance criteria, and issue-to-Git-Flow branch mapping.
Use when recording architectural decisions, querying decision context, validating Lore metadata, or creating Lore-enriched commits in SSPU-AllinOne. Covers local lore status compatibility and required trailer shape.
Use when creating or editing pull requests in SSPU-AllinOne. Covers PR title format, target branch rules, issue links, templates, release labels, merge rules, and Git Flow branch naming.