skills.rest
mintuz
mintuzCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

commit-messages

Writes evidence-backed Conventional Commit messages from staged git diffs.

3|Updated Nov 8, 2014
Search Tags:#git#code review#version control#conventional commits#commit message#atomic commits
One-click install
npx skills add https://github.com/mintuz/.dotfiles --skill commit-messages-mintuz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit-messages
Source: https://github.com/mintuz/.dotfiles/tree/main/agents/.agents/skills/commit-messages
Command: npx skills add https://github.com/mintuz/.dotfiles --skill commit-messages-mintuz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing clear, consistent git commit messages is hard: developers often guess at types, scopes, and motivations, producing vague or inaccurate history. This Skill generates Conventional Commit messages grounded strictly in the staged diff and user-supplied facts, eliminating guesswork. ## Core Features & Use Cases - Evidence-backed messages: Every type, scope, effect, issue number, and metric must trace to the staged diff or user-supplied facts; unsupported claims are omitted with an explanation. - Atomic commit splitting: Detects multiple logical changes and proposes one exact message per commit without mutating the git index. - Full Conventional Commits support: Handles breaking changes with ! and BREAKING CHANGE: footers, reverts with Refs: footers, and proper type/scope selection. - Use Case: Stage a bug fix with its regression test, then ask for a commit message; receive a ready-to-use fix(scope): ... message with a why-focused body wrapped at 72 characters. ## Quick Start Write a conventional commit message for my currently staged changes.

Frequently Asked Questions about commit-messages

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a conventional commit message from a staged diff?▼

Stage your changes with git add, then ask for a commit message. The skill reads the staged diff, selects the correct type and scope from the observed intent, and returns a ready-to-use message with an optional why-focused body.

How to split unrelated changes into atomic commits?▼

Group changes by intent: one commit holds changes that should be reverted together. The skill identifies multiple logical changes, states how their intents differ in one line, and gives an exact message per commit without altering your index.

When should a commit message include a body or footer?▼

Add a body only when it carries motivation the header cannot express, wrapped at 72 characters. Add footers for issue references, breaking changes with a BREAKING CHANGE note, or reverts naming the reverted commit hash.

What happens if the staged diff is missing or evidence is incomplete?▼

If the change itself is missing, the skill stops and asks for the staged diff or a summary. If only motivation is missing, it writes the header and omits the body, naming exactly which parts would be guesswork.

Does this skill write pull request descriptions?▼

No. The skill is scoped strictly to git commit messages following the Conventional Commits specification. PR titles, descriptions, and review text are explicitly out of scope.

Related Skills

Explore More Software Engineering Skills→
yamato0811yamato0811

git-commit-executor

Analyze git changes and create logical Conventional Commits.

Community
Intermediate
MS33834MS33834

Single-Flow PR Yeet

Stages, commits, pushes, and opens a GitHub pull request for a linear change.

Community
Advanced
jtucker9jtucker9

verify

Verify completed work with automated build, test, and lint checks before committing.

Community
Advanced
JiangAustinJiangAustin

chinese-commit-conventions

Standardize Chinese Git commit messages with commitlint, husky, and commitizen.

Community
Intermediate