メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | commit-messages |
| description | 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 this format:
type(scope): 中文摘要
The summary must contain Chinese characters. Scope is optional but recommended.
| Type | Use |
|---|---|
feat | New feature |
fix | Bug fix |
docs | Documentation |
style | Formatting without behavior change |
refactor | Code restructuring |
test | Tests |
chore | Maintenance |
ci | CI / workflow config |
build | Build system |
perf | Performance |
deps | Dependencies |
release | Release preparation metadata |
Bug-fix branches use bugfix/<topic>, but the commit type is still fix.
Use a lowercase, short affected area:
feat(wechat): 添加公众号订阅基础框架
fix(macos): 修复 Runner 构建路径错误
docs(readme): 更新构建说明
ci(actions): 修复 Scorecard 固定 SHA
deps(flutter): 升级 Flutter 工具链
Agent-made commits should be created with Lore:
lore commit -i
Validate the new commit:
lore validate HEAD~1..HEAD
Use repository status helpers when local lore status is unavailable:
pwsh ./scripts/lore/status.ps1
bash ./scripts/lore/status.sh
Use the body for concise rationale. Put Lore trailers as the final contiguous block:
Constraint: <external constraint>
Rejected: <alternative> | <reason>
Confidence: high
Scope-risk: narrow
Directive: <future warning>
Tested: <verification>
Not-tested: <gap>
Use these in the commit body or PR body:
Closes #123 / Fixes #123 / Resolves #123: close on merge.Refs #123: reference without closing.Prefer PR body references when the same branch contains multiple commits.
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 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.