git-commit

Generate formatted git commit messages from project changes.

14|1|Updated Dec 29, 2011
One-click install
npx skills add https://github.com/doitian/dotfiles-public --skill git-commit-doitian
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/doitian/dotfiles-public/tree/main/ai/skills/git-commit
Command: npx skills add https://github.com/doitian/dotfiles-public --skill git-commit-doitian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating consistent, readable git commit messages that clearly convey the change intent and scope.

Core Features & Use Cases

  • Subject formatting: generates a concise, lowercase subject capped at 72 characters.
  • Body with rationale: adds a descriptive body explaining the reasoning and impact of the change.
  • Use Case: ideal for feature work, bug fixes, and refactors to maintain a high-quality project history.

Quick Start

Describe your changes and I will generate a properly formatted git commit message.

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 conventional git commit message from staged changes?

To generate a conventional git commit message, you describe your project changes and the tool analyzes the git status and git diff to craft a descriptive subject and body. It enforces a lowercase subject capped at 72 characters and adds a body explaining the change rationale and impact.

Why does my git commit message need a body explaining the rationale?

A git commit message body explaining the rationale and impact is needed to maintain a high-quality, readable project history. It clearly conveys the change intent and scope for features, bug fixes, and refactors, making it easier for teams to understand the reasoning behind modifications.

Can I use this to enforce coding standards for my version control workflow?

Yes, you can use this to enforce coding standards for your version control workflow. It ensures repository commit subject style consistency by automatically formatting the subject line to lowercase and limiting it to a maximum of 72 characters for every generated commit.

What is the best way to format a git commit subject for feature work and bug fixes?

The best way to format a git commit subject for feature work and bug fixes is to use a concise, lowercase string capped at 72 characters. This approach is applied after analyzing recent commits and current diffs to ensure consistency with your repository's commit subject style.

Does this tool work with existing recent commits to match my repository style?

Yes, the tool works with recent commits to match your repository style. It analyzes your recent project history alongside the current git status and git diff output to ensure the generated commit message aligns with your established coding standards and formatting conventions.