Skills
Commit style skill
Your commit convention as a skill: subjects, bodies, and scopes agents follow exactly.
Last reviewed July 17, 2026
A single-file skill template encoding a conventional-commit style: subject rules, body requirements, and the split test for mixed changes.
SKILL.md
# Commit style Apply when writing or reviewing commit messages in this workspace. ## Subject line - Format: type(scope): description. Types: feat, fix, refactor, docs, test, chore, perf. - Imperative, under 65 characters, states the behavior change: "fix(billing): prevent double-charge on retry", never "fixed some billing stuff". - Scope is the product area, not the file name. ## Body - Required when the change needs a why: 2-6 lines on the reason and any rejected alternative. - Call out side effects the diff implies: config changes, migrations, behavior changes for existing data. - Reference the issue: "Refs: #123" as the last line when one exists. ## The split test If the subject needs "and", propose splitting the commit instead of writing a compound message. One change, one commit, one reviewable story.
Set it up
- 1
Copy the skill body
Swap in your team's types and reference format; delete what you do not enforce, because unenforced rules rot the enforced ones.
- 2
Create the skill
Add it in the workspace Skills page; agents writing commits on connected computers follow it automatically.