git-commit

Generate conventional-commits-formatted commit messages from Git repository changes.

5|Updated Jul 25, 2025
One-click install
npx skills add https://github.com/tomzx/agents --skill git-commit-tomzx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/tomzx/agents/tree/main/skills/git-commit
Command: npx skills add https://github.com/tomzx/agents --skill git-commit-tomzx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates conventional commits from the changes detected in a Git repository.

Core Features & Use Cases

  • Enforces conventional-commit style: types, scopes, and subject lines.
  • Guides users through reviewing changes and composing messages with examples and rules.
  • Use Case: When preparing a PR or release, quickly generate consistent commit messages for all changes.

Quick Start

Draft a commit message following the rules above and run the usual git add and git commit commands.

Frequently Asked Questions about git-commit

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

FAQPage Schema
How do I generate conventional commits from git changes?

You can generate conventional commits by analyzing staged and unstaged repository changes to construct a canonical message. This process enforces type, scope, and subject formatting rules to ensure consistent commit quality.

What is the conventional commit format for a git commit message?

The conventional commit format structures messages using a specific type, scope, and subject line. It provides rules and examples to guide users in composing canonical messages that improve overall commit history readability.

How do I write consistent git commit messages for a PR or release?

To write consistent git commit messages for a PR or release, draft a message following conventional commit rules and execute standard git add and git commit commands. This ensures all changes are consistently formatted.

Does the conventional commit generation process cover unstaged changes?

Yes, conventional commit generation covers both staged and unstaged changes detected in the Git repository. It guides users through reviewing these changes to compose the final commit message accurately.

What are the limitations of automated conventional commit generation?

Automated conventional commit generation focuses strictly on enforcing message formatting and guiding composition. It requires users to manually execute git add and git commit commands after drafting the message.