git-commit

Enforce Conventional Commits format for standardized git commit messages.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate standardized English commit messages that follow the Conventional Commits format, reducing ambiguity and improving changelog readability.

Core Features & Use Cases

  • Enforces English-language commit messages for subject, body, and footer.
  • Supports Conventional Commit types (feat, fix, docs, style, refactor, test, chore).
  • Guides subject line formatting: <type>(<scope>): <subject>, with optional body and footer.
  • Provides an explicit workflow to stage changes and create commits with the generated message.
  • Includes examples and guidelines to assist code reviews and automated tooling.

Quick Start

Craft a conventional-commits compliant commit message for your upcoming change.

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 in English?

It standardizes git commit messages by enforcing the Conventional Commits format, ensuring English-only messages with proper structure for type, scope, subject, body, and footer during commit creation and review.

What is the correct format for a conventional commit subject line?

The correct conventional commit subject line follows the <type>(<scope>): <subject> format. This Skill enforces this structure, applying specific length guidance and supporting standard types like feat, fix, docs, style, refactor, test, and chore.

Can I use this to stage files and create a git commit automatically?

Yes, the Skill provides an explicit execution workflow to stage changes and create commits with the generated message. It guides the process end-to-end, ensuring the commit adheres to the Conventional Commits format.

Does this support all Conventional Commit types like feat and fix?

Yes, it supports standard Conventional Commit types including feat, fix, docs, style, refactor, test, and chore. This ensures your commit messages are properly categorized for changelog generation and automated tooling.

Why enforce English-only conventional commit messages?

Enforcing English-only conventional commit messages reduces ambiguity and improves changelog readability across international teams. This Skill applies the requirement to the subject, body, and footer to assist code reviews and automated tooling.