commit-style

name	commit-style
description	This skill should be used when writing git commit messages, creating git commits, composing pull request titles and descriptions, or when the user asks to "commit", "git commit", "write commit message", "pull request", or "PR description". Provides conventions for subject lines, prefix patterns, body content, and verb choices.
version	0.3.0

Git Commit Style

Conventions for writing git commit messages and pull request descriptions. Project-specific conventions always take priority.

Subject Line

• Try to keep under 50 characters total
• No trailing period
• Lowercase imperative verbs: fix, add, remove, use, avoid, ensure, adjust, allow, enable, extract, introduce, show, move, roll
• Capital letter only when starting with a proper noun or class name — never capitalize verbs
• Embed the "why" directly when possible: avoid enlarging small images, avoid double-save on withdraw
• Technical identifiers kept verbatim: config.x.asset_file_uploadable, event_submission_open?
• Arrow notation for renames: ops-lb: rknw -> rknet

Keeping Under 50 Characters

Techniques when the subject runs long: