commit-messages
/commit-messages
Write commit messages that explain change and intent so history stays useful. Use when committing work or asked to draft a commit message for a diff.
- Author
- Amey-Thakur ↗
- Repository
- AI-SKILLS ↗
- Licence
- MIT
- Last repository change
- 05.09.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 05.09.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Write commit messages that explain change and intent so history stays useful. Use when committing work or asked to draft a commit message for a diff.
Original author description
Write commit messages that explain change and intent so history stays useful. Use when committing work or asked to draft a commit message for a diff.
How it works
- Method
- Litmus tests
- Boundaries
SKILL.md preview
--- name: commit-messages description: Write commit messages that explain change and intent so history stays useful. Use when committing work or asked to draft a commit message for a diff. --- # Commit messages A commit message is documentation with a captive audience: everyone who ever runs `git blame` on this line. Write for the person debugging at 2 a.m. two years from now. ## Method 1. **One change per commit.** If the diff mixes a bug fix with a rename and a formatting pass, split it before writing anything. A message cannot be honest about three changes at once. 2. **Subject line: imperative, ≤ 50 characters, no trailing period.** "Fix stale cache on user switch", not "Fixed some caching issues". The test: the subject completes the sentence *"If applied, this commit will ..."*. 3. **Body: the why, not the what.** The diff already shows what changed. The body carries what the diff cannot: why this approach, what else was tried, what breaks without it, which trade-off was accepted. Wrap at 72 characters. A one-line body beats a missing one: "Without this, deleting a notebook left its documents in search results." 4. **Reference, don't recount.** Link the issue or incident instead of restating it; state behavior instead of narrating your afternoon. 5. **Never write these subjects:** "fix", "wip", "updates", "address comments", "more changes". Each is a hole in history exactly where someone will need a rope. ## Litmus tests - Could a reviewer decide whether to cherry-pick this commit onto a release branch from the message alone? - Does the message still make sense with no access to the pull request, the chat thread, or you? - If this commit causes a regression, does the message give the person reverting it enough context to know what they are giving up? ## Boundaries Follow the repository's existing convention when one exists (Conventional Commits prefixes, issue-tag prefixes, co-author trailers): consistency in a shared history outranks personal taste. This skill governs the content; the project governs the shape.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · Amey-Thakur/AI-SKILLS | 90 | MIT |
| finolabs/finolabs-vibecode | 100 | MIT |
| leanstacks/lstk | 100 | MIT |
| athola/claude-night-market | 100 | MIT |
| TheDecipherist/claude-code-mastery | 100 | MIT |
Database snapshot: 13.11.2026 · package version 1f5b2e3046fb (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100commit-message
Generate conventional commit messages - use when creating commits, writing commit messages, or asking for git commit help - 84generate-commit-message
Generate well-structured git commit messages. Use when user says "generate commit message", "write a commit", "what should my commit message be", "create commit message for these changes", or needs help crafting conventional commit messages. - 100pr-commit-message
Write or improve high-signal PR merge commit messages and squash commit messages. Use this whenever the user says "create a commit message for this PR", "write a merge commit message", "draft the squash commit body", "improve this commit message", or asks for a message that… - 100commit
Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue re... - 100commit
Analyze git diffs or staged changes and generate conventional commit messages that explain WHY a change was made. Supports auto-detecting type and scope, intelligent file staging, and interactive overrides. Use when asked to "write a commit message", "generate a commit",… - 100sentry-commit-messages
Create commit messages following Sentry conventions with conventional commits and issue references. Use when committing code changes, writing commit messages, or formatting git history with Fixes/Refs patterns.