skills.rest
ChenYCL
ChenYCLCOMMUNITY
Explore all skills by this author →
GitHub

git-commit

Generate semantic Git commit messages following the Conventional Commits specification.

1|Updated Feb 5, 2026
Search Tags:#git#developer tools#version control#commit#conventional commits
One-click install
npx skills add https://github.com/ChenYCL/claude-skills-collection --skill git-commit-chenycl
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/ChenYCL/claude-skills-collection/tree/main/git-commit
Command: npx skills add https://github.com/ChenYCL/claude-skills-collection --skill git-commit-chenycl

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of clear, consistent, and informative Git commit messages, adhering to the Conventional Commits specification.

Core Features & Use Cases

  • Conventional Commits: Generates messages following the <type>(<scope>): <description> format.
  • Guideline Enforcement: Provides rules for subject lines, bodies, and footers.
  • Use Case: After completing a bug fix, you can ask this Skill to generate a commit message like fix(api): resolve null response error with an optional body explaining the fix and referencing the issue number.

Quick Start

Use the git-commit skill to generate a commit message for a new feature that adds user authentication.

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 for git automatically?▼

To generate conventional commit messages, you need a structured format like `<type>(<scope>): <description>`. This skill automates creating these semantic messages, ensuring version control best practices and changelog consistency.

What is the conventional commits format for a git fix?▼

The conventional commits format for a git fix is `fix(<scope>): <description>`. This skill generates messages following this specification, supporting types like feat, fix, docs, optional scopes, descriptive subjects, and detailed bodies.

How do I write a git commit message body and footer for breaking changes?▼

A git commit message body explains the fix, while footers reference breaking changes or issue numbers. This skill facilitates generating these components, adhering to conventional commits guidelines for code review consistency.

Can I use this to generate a commit message for a new feature?▼

Yes, you can generate a commit message for a new feature. This skill produces semantic messages like `feat(api): add user authentication`, supporting various commit types to facilitate version control best practices.

Does generating semantic git commits require manual guideline enforcement?▼

Generating semantic git commits does not require manual guideline enforcement. This skill provides rules for subject lines, bodies, and footers automatically, ensuring your commit messages adhere to the conventional commits specification.

Related Skills

Explore More Software Engineering Skills→
cursor-jscursor-js

git-commit

Analyze code diffs and generate Conventional Commits messages.

Official
Intermediate
ccfccf

changelog-automation

Generate CHANGELOG.md from commits, PRs, and releases using Keep a Changelog.

Community
Advanced
maroffomaroffo
16

source-control

Standardize Git commit messages and branching strategies with conventional commit formats.

Community
Intermediate
vndkubivndkubi

conventional-commit

Generate conventional commit messages from staged changes.

Community
Intermediate