git-commit

Generate and validate Git commit messages following the Conventional Commits specification.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/AnthemFlynn/ccmp --skill git-commit-anthemflynn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/AnthemFlynn/ccmp/tree/main/plugins/git-commit/skills/git-commit
Command: npx skills add https://github.com/AnthemFlynn/ccmp --skill git-commit-anthemflynn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps you craft clear, conventional commit messages following the Conventional Commits spec, reducing ambiguity and review time.

Core Features & Use Cases

  • Smart analysis of staged changes to suggest a fitting type, scope, and description.
  • Slash commands like /commit, /validate, /changelog, and /version to speed up Git workflows.
  • Guided formatting ensures messages follow the established convention with optional body and footer.

Quick Start

Stage your changes with git add <files>, then ask Claude to help by saying "help me commit" or use the slash commands such as /commit. Claude will propose a message like feat(api): add OAuth2 authentication and you can apply it with git commit -m"feat(api): add OAuth2 authentication".

Frequently Asked Questions about git-commit

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

FAQPage Schema
How do I write conventional commit messages automatically?

Conventional commits are a standardized format specifying commit type (feat, fix, etc.), optional scope, and description. This Skill analyzes your staged changes and generates messages following the Conventional Commits specification, reducing ambiguity in Git workflows and speeding up code review.

Can I automate commit messages based on my staged changes?

Yes. Stage your changes with git add, then request help with commit formatting. The Skill analyzes the diff, suggests an appropriate type and scope, and generates a complete message you can apply directly with git commit.

What's the best way to enforce consistent commit message formatting in a Git workflow?

The Conventional Commits specification provides strict formatting rules for type, scope, and description. This Skill validates messages against those rules, detects breaking changes, and integrates validation scripts into your automation pipeline to ensure consistency across commits.

Do slash commands work with Git commit automation?

Yes. Slash commands like /commit, /validate, /changelog, and /version accelerate Git workflows by triggering specific commit operations directly without manual typing.

How do I detect breaking changes and generate semantic versions from commits?

The Skill integrates analysis, validation, and version-detection scripts. It identifies breaking changes in commit messages, generates appropriate semantic version bumps, and produces changelog entries from your commit history automatically.

Can conventional commits work with feature branches and pull request workflows?

Yes. Conventional commits apply broadly within Git workflows across any branching strategy. The Skill handles features, fixes, and breaking changes consistently, making pull request review and changelog generation more efficient.