generating-smart-commits

Generate conventional commit messages from staged Git changes.

2.6k|379|Updated Oct 10, 2025
One-click install
npx skills add https://github.com/jeremylongshore/claude-code-plugins-plus --skill generating-smart-commits
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: generating-smart-commits
Source: https://github.com/jeremylongshore/claude-code-plugins-plus/tree/main/plugins/devops/git-commit-smart/skills/git-commit-smart
Command: npx skills add https://github.com/jeremylongshore/claude-code-plugins-plus --skill generating-smart-commits

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This skill empowers Claude to create well-formatted, informative commit messages automatically. By analyzing staged changes, it generates messages that adhere to conventional commit standards, saving developers time and ensuring consistency in Git history.

Core Features & Use Cases

  • AI-Driven Commit Messages: Automatically determine commit type (feat, fix, docs) and scope.
  • Conventional Commit Standards: Format messages according to industry best practices.
  • Breaking Change Detection: Identify and flag breaking changes in the commit message.
  • Use Case: After staging changes for a new user authentication module, automatically generate a commit message like feat(auth): Implement user authentication module.

Quick Start

User request: "Generate a commit message for adding user authentication"

The skill will:

  1. Analyze the staged changes related to user authentication.
  2. Generate a commit message like: feat(auth): Implement user authentication module.
  3. Present the message to the user for confirmation.

Frequently Asked Questions about generating-smart-commits

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

FAQPage Schema
How do I automatically generate conventional commit messages from staged changes?

Use the /commit-smart or /gc command after staging your Git changes. Claude analyzes the staged diff, determines the commit type (feat, fix, docs, etc.), identifies the scope, detects breaking changes, and generates a conventional commit message for your confirmation before committing.

What is a conventional commit and why should I use one?

Conventional commits are standardized Git messages following the format type(scope): description, enabling automated changelog generation and consistent project history. They improve code review clarity, simplify debugging, and make version bumping automated across teams.

Can this detect breaking changes in my commit?

Yes. When analyzing staged changes, the skill identifies breaking changes and flags them in the generated message, typically appending a BREAKING CHANGE footer to alert other developers and tooling of API or behavior modifications.

Do I need to know commit type conventions to use this?

No. Claude infers the appropriate commit type (feat, fix, docs, refactor, etc.) by analyzing your staged code changes, so you don't need to manually select or remember conventional commit categories.

What happens if I don't have staged changes when I run /commit-smart?

The skill requires staged Git changes to function. If nothing is staged, the command won't generate a message. Stage your changes first using git add, then invoke /commit-smart or /gc.

Can I edit the generated commit message before confirming?

Yes. The skill presents the generated conventional commit message for your review and confirmation, allowing you to modify, accept, or reject it before the commit is finalized.