format-git-commit

Generate conventional git commit messages from staged and unstaged changes.

Updated Jun 4, 2025
One-click install
npx skills add https://github.com/alexei-lexx/budget --skill format-git-commit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: format-git-commit
Source: https://github.com/alexei-lexx/budget/tree/main/.claude/skills/format-git-commit
Command: npx skills add https://github.com/alexei-lexx/budget --skill format-git-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically generate a clean, well-structured git commit message from your current changes, saving time and improving history readability.

Core Features & Use Cases

  • Deterministic commit messages based on the actual diffs of staged changes.
  • Handles both staged and unstaged changes, including untracked files, to produce an accurate summary.
  • Enforces an imperative subject line and provides an optional detailed body with bullet points describing the changes.
  • Suitable for quick commits during code reviews or when preparing a changelog entry.

Quick Start

Run format-git-commit when you are about to commit to generate a ready-to-use commit message.

Frequently Asked Questions about format-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?

To generate a git commit message from staged changes, run the format-git-commit command. It analyzes your staged diffs first, then all changes if none are staged, and outputs a ready-to-use message following conventional commit style.

What is the best way to write conventional commit messages automatically?

The best way to write conventional commit messages automatically is to use a diff analysis tool like format-git-commit. It enforces an imperative subject line and provides an optional detailed body with bullet points describing the actual changes.

Can I generate a commit message if I have unstaged or untracked files?

Yes, you can generate a commit message with unstaged or untracked files. The tool analyzes staged changes first, but if none are staged, it evaluates all changes including untracked files to produce an accurate summary.

How does a conventional commit message formatter handle working tree diffs?

A conventional commit message formatter handles working tree diffs by analyzing the actual file modifications to produce a deterministic message. It creates a concise subject line and an optional body with bullet points describing the changes.

When do I need an automated git commit message generator?

You need an automated git commit message generator when preparing to commit during code reviews or preparing a changelog entry. It saves time and improves history readability by automatically summarizing your current working tree changes.

Does the generated commit message include a detailed body or just a subject line?

The generated commit message includes both a concise subject line and an optional detailed body. The body uses bullet points to describe the changes, providing a clean, well-structured summary of your current working tree diffs.