菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | pr-writing |
| description | 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. |
Use this skill before creating or editing a PR.
Format:
type(scope): 中文摘要
Allowed types: feat, fix, docs, style, refactor, test, chore, ci, build, perf, deps, release.
Bug-fix branches are named bugfix/<topic>, but PR title type remains fix.
develop.develop.main is develop -> main release promotion or default-branch synchronization.main.Expected source branches:
feature/<topic>
bugfix/<topic>
docs/<topic>
chore/<topic>
refactor/<topic>
test/<topic>
ci/<topic>
deps/<topic>
release/vX.X.X[-channel]
hotfix/<topic-or-version>
Optional personal prefixes such as qintsg/feature/<topic> are allowed.
Use the PR body:
Closes #278
Refs #123
Use closing keywords only when merging the PR should close the issue.
Use .github/pull_request_template.md for regular PRs. Fill:
Use .github/PULL_REQUEST_TEMPLATE/release.md for Release PRs.
Only manually add release to legal Release PRs:
release/vX.X.X-alpha|beta|rc -> develop # with release label
develop -> main # with release label for stable/lts/hotfix
Do not add release to the first release/vX.X.X -> develop stable/lts/hotfix prep PR.
Run checks that match the changed surface:
dart format --set-exit-if-changed <changed-dart-files>
flutter analyze --no-fatal-infos
flutter test
python scripts/ci/validate_github_governance.py
lore validate origin/develop..HEAD
If a check cannot run on the current platform, state the reason and the next-best validation.
develop -> main: merge commit only; no squash or rebase.develop or main.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 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.