菜单
Use when creating git commits, staging changes, or writing commit messages - defines commit format rules, conventional commits usage, ticket-branch handling, and AI attribution requirements
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when starting a new feature, design change, or architecture decision. Explores approaches and tradeoffs before planning or coding. NEVER skip this for non-trivial work.
Use when executing an implementation plan. Each step is delegated to a fresh subagent for isolated context, then reviewed before proceeding. Do NOT execute plans inline — use subagents.
Use when implementation is complete and you need to decide how to integrate the work - guides completion by presenting structured options for merge, PR, or cleanup
Use when creating implementation plans. Breaks work into small, verifiable steps with exact file paths and verification commands. Use after brainstorming approval.
Use when you receive code review feedback (from a reviewer subagent, /review command, or human). Guides proper processing of feedback without dismissing or cherry-picking.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
| name | creating-a-commit |
| description | Use when creating git commits, staging changes, or writing commit messages - defines commit format rules, conventional commits usage, ticket-branch handling, and AI attribution requirements |
Check the current branch name to decide which header format to use:
digraph format_selection {
"Branch name?" [shape=diamond];
"Ticket format\n<ticket>: <description>" [shape=box];
"Conventional format\n<type>[scope]: <description>" [shape=box];
"Branch name?" -> "Ticket format\n<ticket>: <description>" [label="matches ticket pattern\ne.g. MPCC-1234"];
"Branch name?" -> "Conventional format\n<type>[scope]: <description>" [label="anything else"];
}
When the branch name matches a ticket pattern (e.g. MPCC-1234, MPMX-42),
the ticket replaces the type prefix:
<ticket>: <description>
[optional body]
Assisted-by: <model name> via <tool name>
When the branch does not match a ticket pattern, use Conventional Commits:
<type>[optional scope]: <description>
[optional body]
Assisted-by: <model name> via <tool name>
Types: feat, fix, build, chore, ci, docs, style, refactor, perf, test
feat — new feature (correlates with SemVer MINOR)fix — bug fix (correlates with SemVer PATCH)! after type/scope for breaking changes (correlates with SemVer MAJOR)fix(parser): handle empty inputThese apply to both formats:
The entire commit message MUST be lowercase. Exceptions:
NixOS, GitHub, Pi)Assisted-by trailer key (standard git trailer convention)Assisted-by value (e.g. Claude Opus 4)Optional. Describe the why, not the what. May use prose or bullet points. Must be separated from the header by a blank line.
Assisted-by Trailer)Mandatory on every commit an AI agent creates, including trivial ones.
Per Xe Iaso's convention and Fedora's AI-Assisted Contributions Policy.
Assisted-by lines.MPCC-34: add opencode global agent rules
add programs.opencode.rules with conventional commit enforcement,
lowercase policy, and assisted-by trailer requirement so all ai
agents produce consistent, machine-readable commit messages.
Assisted-by: Claude Opus 4 via Pi
feat(opencode): add skill for commit message formatting
Assisted-by: Claude Sonnet 4 via Pi
fix: resolve grafana service breakage after upgrade
the grafana module changed its systemd unit name in the latest
nixpkgs update, breaking the existing service override.
Assisted-by: GPT-4o via Pi
chore: update flake lock
Assisted-by: Claude Opus 4 via Pi