القائمة
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.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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 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 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.
| name | branch-checkout |
| description | 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. |
Create a task branch before investigating or editing an issue.
Issue -> sync develop -> choose branch type -> create branch -> verify branch -> investigate/edit
git status --short --branch
git checkout develop
git pull --ff-only origin develop
If unrelated local changes exist, do not discard them unless the user explicitly asks. Stash only when needed and safe.
| Issue or task | Branch prefix | Command |
|---|---|---|
[Feature] / enhancement | feature/ | <git-flow> feature start <name> |
[Bug] / failing behavior | bugfix/ | <git-flow> bugfix start <name> |
[Docs] | docs/ | git checkout -b docs/<name> |
| CI / workflow / governance | ci/ | git checkout -b ci/<name> |
| Dependency update | deps/ | git checkout -b deps/<name> |
| Refactor | refactor/ | git checkout -b refactor/<name> |
| Tests | test/ | git checkout -b test/<name> |
| Maintenance task | chore/ | git checkout -b chore/<name> |
| Release prep | release/ | <git-flow> release start vX.X.X[-channel] |
| Emergency hotfix coordination | hotfix/ | <git-flow> hotfix start <name> |
The branch prefix for bug fixes is bugfix/, not fix/. Commit and PR titles still use fix(scope): 中文摘要.
Examples:
# Issue #278: 全面配置并启用 Git Flow 工作流
<git-flow> feature start git-flow-setup
# Issue #287: Scorecard SHA 错误
<git-flow> bugfix start scorecard-243-sha
# Documentation task
git checkout -b docs/release-governance
# Workflow task
git checkout -b ci/github-actions-upgrade
Use a short kebab-case topic. Include the issue number only when it improves traceability.
<git-flow> means the command surface available on the machine: gitflow on this Windows checkout, or git flow on installations that expose Git Flow as a Git subcommand.
git branch --show-current
git status --short --branch
The active branch must not be develop or main.
git push -u origin <branch>.develop, except explicit develop -> main promotion.