git-commit-message

Generates Git commit messages from staged changes with proper formatting.

11|2|Updated Dec 14, 2025
One-click install
npx skills add https://github.com/bkircher/skills --skill git-commit-message-bkircher
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit-message
Source: https://github.com/bkircher/skills/tree/main/git-commit-message
Command: npx skills add https://github.com/bkircher/skills --skill git-commit-message-bkircher

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you generate clear, concise, and effective Git commit messages that adhere to best practices, improving code history readability and maintainability.

Core Features & Use Cases

  • Subject Line Generation: Creates a capitalized, imperative subject line within 50 characters.
  • Body Explanation: Formulates a detailed body explaining the 'what' and 'why' of the changes, wrapped at 72 characters.
  • Staged Changes Focus: Ensures the commit message only reflects changes currently staged in your Git index.
  • Use Case: After making several code modifications, you need to commit them. This skill will analyze your staged changes and produce a well-formatted commit message ready to be used.

Quick Start

Use the git-commit-message skill to create a commit message for your staged changes.

Frequently Asked Questions about git-commit-message

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

FAQPage Schema
How do I generate a Git commit message for staged changes?

To generate a Git commit message, the skill analyzes your staged changes and creates a concise subject line within 50 characters and a detailed body wrapped at 72 characters explaining the modifications.

What are the rules for writing great Git commit messages?

Writing great Git commit messages involves following seven rules: using imperative mood, capitalizing the subject line, keeping it under 50 characters, and wrapping the body at 72 characters to explain changes.

Does this tool generate commit messages for unstaged Git changes?

No, this tool does not generate messages for unstaged changes. It strictly analyzes changes currently staged in your Git index to ensure the commit message accurately reflects what is being committed.

What is the best way to format a Git commit message body?

The best way to format a Git commit message body is to wrap text at 72 characters and provide detailed explanations of the 'what' and 'why' of the changes, ensuring clarity for future version control history.

Why should I use imperative mood in a Git commit message?

You should use imperative mood in a Git commit message because it adheres to standard Git best practices, matching built-in Git commands and ensuring the subject line concisely summarizes the action performed.