git-commit

Generate concise git commit messages from staged code changes.

Updated Apr 12, 2026

Search Tags:#git #best practices #commit messages #subject line #generate #staged changes #imperative mood

Ready to run

npx skills add https://github.com/mguinada/agent-skills --skill git-commit-mguinada

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/mguinada/agent-skills/tree/main/skills/git-commit
Command: npx skills add https://github.com/mguinada/agent-skills --skill git-commit-mguinada

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams generate clear, concise git commit messages from changes staged in their repository, improving history readability and collaboration.

Core Features & Use Cases

Automated Subject Lines: Generate short, descriptive subject lines that summarize the change.
Informative Bodies: Provide optional detailed body text with rationale, impact, and references.
Use Case: When performing regular commits, use this Skill to ensure messages adhere to project conventions and best practices.

Quick Start

Stage changes with git add -A, then request a generated commit message from the Skill for the staged changes. For example, "Generate a concise commit message for current changes."

Frequently Asked Questions about git-commit

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

FAQPage Schema

How do I generate a git commit message from staged changes?▼

You can generate a git commit message from staged changes by staging your files with git add and requesting a generated message. The resulting commit message summarizes the staged code changes concisely while adhering to project conventions.

What are the best practices for git commit message subject lines?▼

Best practices for git commit message subject lines include keeping them under 50 characters, using imperative mood, and ensuring proper punctuation. This Skill validates your subject lines against these rules to improve repository history readability.

How do I write informative git commit message bodies?▼

To write informative git commit message bodies, provide detailed text explaining the rationale, impact, and references for your changes. This Skill enforces a 72-character line limit for body text to maintain clear and readable project history.

Does this git commit message generator work with refactoring and feature fixes?▼

Yes, this git commit message generator works with typical Git workflows including feature work, fixes, and refactoring. It applies standard commit best practices across these diverse development scenarios to ensure clear history.

What is the best way to automate descriptive commit messages for my repository?▼

The best way to automate descriptive commit messages is to use a generation tool that analyzes your staged changes and enforces formatting rules. This approach ensures concise, descriptive history without manual formatting effort.