commit

Generate conventional Git commit messages from staged code changes.

Updated Dec 22, 2025

Search Tags:#git #code review #version control #development workflow #commit #conventional commits

Ready to run

npx skills add https://github.com/royhenengel/Claude-Customizations --skill commit-royhenengel

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/royhenengel/Claude-Customizations/tree/main/skills/Git/commit
Command: npx skills add https://github.com/royhenengel/Claude-Customizations --skill commit-royhenengel

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation of well-formatted, conventional Git commits, ensuring consistency and clarity in your project's version history.

Core Features & Use Cases

Automated Commit Message Generation: Analyzes staged changes and suggests commit type, scope, and description based on conventional commit standards.
Type Determination: Guides you in selecting the correct commit type (feat, fix, docs, etc.).
Scope Identification: Helps identify the relevant module or component for the commit.
Use Case: After completing a bug fix, you can use this Skill to generate a fix commit message with the appropriate scope and a clear description of the problem solved.

Quick Start

Use the commit skill to create a conventional commit for your staged changes.

Frequently Asked Questions about commit

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

FAQPage Schema

How do I generate conventional commit messages for staged Git changes?▼

To generate conventional commit messages, this Skill analyzes your staged Git changes to automatically determine the commit type, scope, and description based on your project conventions.

What is the best way to enforce subject line length and body wrapping in conventional commits?▼

Enforcing subject line length and body wrapping in conventional commits is handled automatically by the Skill, which formats the output to meet version control clarity standards.

How does automated type determination work for Git commits?▼

Automated type determination for Git commits works by analyzing staged code changes to guide you in selecting the correct conventional commit type, such as feat, fix, or docs.

Can I use this to identify the correct scope for a bug fix commit?▼

Yes, you can use this Skill to identify the relevant module or component for your commit, generating a fix commit message with the appropriate scope and problem description.

Does this Skill add breaking change notations to version control history?▼

Yes, this Skill enforces breaking change notations in your Git commit messages to ensure clear communication of breaking updates in your version control history.

Why should I use automated conventional commits instead of writing Git messages manually?▼

Using automated conventional commits instead of manual Git messages ensures consistency and clarity in your project's version history by standardizing commit type, scope, and formatting.