skills.rest
DauQuangThanh
DauQuangThanhCOMMUNITY
Explore all skills by this author →
GitHub

git-commit

Generate conventional git commit messages with type, scope, and subject.

14|11|Updated Dec 1, 2025
Search Tags:#automation#git#workflow#templates#version-control#conventional-commits#commit-messages
One-click install
npx skills add https://github.com/DauQuangThanh/hanoi-rainbow --skill git-commit-dauquangthanh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/DauQuangThanh/hanoi-rainbow/tree/main/skills/git-commit
Command: npx skills add https://github.com/DauQuangThanh/hanoi-rainbow --skill git-commit-dauquangthanh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Standardizes and guides the creation of git commit messages to improve readability, traceability, and automation across development teams.

Core Features & Use Cases

  • Enforces conventional commit structure with type, optional scope, and descriptive subject.
  • Supports atomic, well-scoped commits and automatic body/footers guidance for changes requiring context.
  • Provides templates, examples, and best-practices for consistent commit history in code reviews and release processes.

Quick Start

Create a clear, conventional commit using the standard type(scope): subject format.

Frequently Asked Questions about git-commit

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

FAQPage Schema
How do I automate conventional commit messages for my git workflow?▼

You can automate conventional commit messages by applying templates that enforce standard types, optional scopes, descriptive subjects, and body or footer guidance for better traceability.

What is the conventional commit format for structuring code changes?▼

The conventional commit format structures code changes using a standard type, an optional scope, and a descriptive subject, ensuring atomic commits and a consistent history for code reviews.

How do I write atomic commits with proper body and footer context?▼

Writing atomic commits with proper context requires applying conventional commit standards, using templates to separate the subject from the body and footers for changes requiring additional explanation.

Can I use templates to enforce commit message standards across repositories?▼

Yes, you can use templates to enforce commit message standards across repositories, providing best-practice guidance for compliant messages and consistent release processes in version control.

Does this approach support automatic generation of commit types and scopes?▼

This approach supports automatic generation by applying conventional commit standards to code changes, guiding the selection of standard types and optional scopes to limit subject length.

Related Skills

Explore More Software Engineering Skills→
mgoodman60mgoodman60

commit

Generate descriptive Git commit messages from repository changes with conventional formatting.

Community
Basic
4lerman4lerman

release-manager

Automate changelog generation, version bumping, and release planning from git history.

Community
Advanced
mpetitompetito

pr-management

Manage GitHub pull request review threads, comments, and branch merges.

Community
Intermediate
codysumpter-cloudcodysumpter-cloud
2

chinese-commit-conventions

Enforce Chinese-friendly Conventional Commits format with commitlint integration.

Community
Basic