commit

Name: commit
Availability: InStock
Author: ahonn

Generate Conventional Commits 1.0.0 messages for staged changes.

62|2|Updated Feb 21, 2017

Search Tags:#automation #git #versioning #commit #conventional-commits #message-format

Ready to run

npx skills add https://github.com/ahonn/dotfiles --skill commit-ahonn

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps you create conventional commit messages that follow the 1.0.0 specification for staged changes, ensuring consistent history and easier semantic versioning.

Core Features & Use Cases

Determines appropriate commit type (feat, fix, docs, style, etc.) and optional scope from your changes.
Constructs a compliant subject line and optional body and footers according to the Conventional Commits 1.0.0 spec.
Validates and guides message structure, and does not modify your repository unless you explicitly run a commit.

Quick Start

Generate a conventional commit message for the currently 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 for staged git changes, the skill analyzes your repository, determines the correct commit type and scope, and constructs a compliant subject line and body according to the Conventional Commits 1.0.0 specification.

What is the conventional commits format and how does it handle breaking changes?▼

The conventional commits format structures messages with a type, optional scope, subject, body, and footers. It explicitly supports breaking change footers to clearly flag incompatible API modifications for automated semantic versioning.

Does this conventional commits tool modify my working tree or run a commit automatically?▼

This conventional commits tool does not modify your working tree or run a commit automatically. It validates and guides the message structure, only executing the local commit or pipeline update when you explicitly instruct it to.

Can I use conventional commits for automated pipelines and local commits?▼

Yes, you can apply conventional commits across local commits, pull requests, and automated pipelines. The skill enforces the 1.0.0 message format for features, fixes, docs, and chore updates without altering your working tree.

How do I determine the correct commit type and scope for my staged changes?▼

To determine the correct commit type and scope for your staged changes, the skill analyzes your staged changes and automatically maps the modifications to appropriate conventional commit types like feat, fix, docs, or style.