菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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 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 | issue-writing |
| description | 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 GitHub Issue Forms under .github/ISSUE_TEMPLATE/.
| Template | Title prefix | Use when |
|---|---|---|
bug_report.yml | [Bug] | Crash, error, regression, wrong behavior |
feature_request.yml | [Feature] | New feature or enhancement |
docs.yml | [Docs] | Documentation issue |
tasks.yml | [Task] | Clear engineering or governance task |
question.yml | [Question] | Usage or clarification question |
release_request.yml | [Release] | Release preparation |
info_site_request.yml | [Feature] | New website data source |
P0, P1, P2, or P3.Do not include passwords, tokens, cookies, keystores, private keys, real user identifiers, or screenshots that expose credentials. Redact logs before posting.
bug, enhancement, documentation, task, or question.needs-triage is applied once when the issue opens.P0-P3), platform labels, and module labels can be inherited by linked PRs.release label is not auto-applied by issue templates.Use this mapping when moving from issue writing to implementation:
| Issue | Branch prefix | PR title type |
|---|---|---|
[Bug] | bugfix/ | fix |
[Feature] | feature/ | feat |
[Docs] | docs/ | docs |
[Task] CI/workflow | ci/ | ci |
[Task] dependencies | deps/ | deps |
[Task] refactor | refactor/ | refactor |
[Task] tests | test/ | test |
[Task] maintenance | chore/ | chore |
[Release] | release/ | release |
Bug fixes use branch prefix bugfix/; do not create new fix/ branches.