commit

Generate conventional commit messages from staged git diffs.

Updated Apr 10, 2026

Search Tags:#automation #git #commit #pre-commit #messages #conventional-commits #scopes

Ready to run

npx skills add https://github.com/erichugy/agentic.skills --skill commit-erichugy

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/erichugy/agentic.skills/tree/main/commit
Command: npx skills add https://github.com/erichugy/agentic.skills --skill commit-erichugy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Commit messages are often inconsistently formatted and manually crafted, slowing reviews and releases. This Skill analyzes changes and generates standardized, conventional commit messages that reflect the nature of the change.

Core Features & Use Cases

Analyze git diffs to infer type (feat, fix, docs, chore, etc.), scope, and a concise subject.
Generate and format messages according to the Conventional Commits specification for automated release notes and changelogs.
Integrate with pre-commit hooks or CI pipelines to ensure every commit adheres to the conventional format in common workflows.

Quick Start

Provide a summary of the changes, and I will generate a conventional commit message for the 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 automatically from staged changes?▼

Generate conventional commit messages by evaluating git diffs to infer the type, scope, and concise subject for staged changes. This process formats messages according to the Conventional Commits specification without altering unstaged changes.

Can I use a pre-commit hook to enforce conventional commit syntax in CI pipelines?▼

Yes, you can integrate conventional commit message generation with pre-commit hooks or CI pipelines. This ensures every commit adheres to the conventional format across common workflows, automating syntax enforcement during development.

What conventional commit types and scopes are supported for automated message generation?▼

Supported conventional commit types include feat, fix, docs, chore, style, and refactor. The automated generation also supports breaking-change scopes, evaluating diffs to infer the appropriate type and scope for the commit message.

How do I format breaking changes in automated conventional commit messages?▼

Format breaking changes by evaluating git diffs and inferring the breaking-change scope for the conventional commit message. The generation process enforces conventional syntax to properly reflect the nature of the breaking change.

Does automated conventional commit generation modify unstaged changes in my repository?▼

No, automated conventional commit generation evaluates staged git diffs to infer type, scope, and subject while explicitly avoiding altering unstaged changes. This ensures only staged changes are analyzed for message generation.