Git Commit Message Generator

Automatically generate professional, Conventional Commit messages from your git diffs.

Install
cmdop skills install agensi-git-commit-message-generator

Git Commit Message Generator is a skill that takes git diffs as input and produces commit messages formatted to the Conventional Commits specification. It classifies each change into one of the standard types — feat, fix, refactor, docs, style, test, or chore — using a decision heuristic designed to distinguish between similar categories such as refactor and style. The skill enforces the 50/72 formatting rule, keeping subject lines at or under 50 characters and wrapping body text at 72 characters. When a change introduces a breaking API or behavior, the skill detects this and applies the required exclamation-mark syntax along with the appropriate footer. All messages are written in the imperative mood for consistency across the project history. The skill can work with staged changes, unstaged changes, or a specific set of file paths, giving it accurate context before generating the message. Because it follows Conventional Commits, repositories using automated changelog and release tools such as semantic-release can consume its output directly without manual reformatting. This skill is not a general-purpose Git client — it has no tools for branching, merging, pushing, or any other Git operations. Its scope is solely generating commit message text from diff input.

Use cases

  • Generate a properly typed and formatted commit message from a staged git diff
  • Detect breaking changes in a diff and produce the correct '!' syntax and footer automatically
  • Enforce the 50/72 formatting rule across all commits in a project
  • Produce commit messages ready for consumption by semantic-release or similar changelog tools
  • Classify ambiguous changes between refactor, style, or chore types without manual judgment
  • Generate commit messages scoped to specific file paths for granular commits

When to use it

  • The project follows or wants to adopt the Conventional Commits specification
  • Automated changelog generation or semantic versioning tools are part of the release pipeline
  • Consistent commit message formatting across a team is required
  • Staged or unstaged diff content is available to pass as input

When not to use it

  • Git operations beyond message generation are needed — this skill does not branch, merge, push, or stage files
  • The project uses a commit message convention other than Conventional Commits
  • No git diff content is available to analyze
  • A full Git MCP server with repository management tools is required