git-commit

Generate conventional commit messages from a summary of changes.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/DennisToma/repo_example --skill git-commit-dennistoma
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/DennisToma/repo_example/tree/main/.claude/skills/git-commit
Command: npx skills add https://github.com/DennisToma/repo_example --skill git-commit-dennistoma

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developers often struggle to produce consistent, conventional commit messages, making changelogs and project histories harder to read and automate.

Core Features & Use Cases

  • Enforces conventional commits style across a repository to standardize history
  • Guides proper types (feat, fix, docs, style, refactor, test, chore) and optional scopes for clarity
  • Generates and validates commit messages from a brief summary of changes, suitable for both small and large commits

Quick Start

Provide changed files and a brief description of changes, then request a conventional commit message in the form type(scope): subject. Example: feat(auth): add login flow

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 commit messages from a summary of changes?

Conventional commit messages require a standardized format of type(scope): subject. This skill enforces that structure by validating types like feat or fix and guiding proper scopes for clarity across repository edits.

What types and scopes should I use for conventional commits?

Conventional commits use specific types like feat, fix, docs, style, refactor, test, and chore. You apply an optional scope in parentheses to clarify the affected module before writing the subject line.

How do I write a conventional commit for a bug fix?

To write a conventional commit for a bug fix, you use the fix type with an optional scope, formatting it as fix(scope): subject. The skill validates this structure from your provided change summary.

Can I automate git commit message generation for large repository edits?

Yes, you can automate git commit message generation for large edits by providing a brief description of the changes. The skill is suitable for both small and large commits and outputs a validated conventional message.

Why do my git commit messages fail conventional commits validation?

Git commit messages fail conventional commits validation when they lack the required type, scope, or subject formatting. This skill enforces the specification to ensure proper types and structure are applied consistently.