commit

Convert git diffs into Conventional Commits compliant commit messages.

1|Updated Jan 3, 2022

Search Tags:#git #cli #diff #generate #version-control #commit-message #conventional-commits

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill converts git diffs into conventional commit messages, reducing manual effort and ensuring consistent commit history.

Core Features & Use Cases

Converts staged changes into a Conventional Commits compliant message with type, scope, and subject.
Supports multi-change commits by proposing multiple messages when needed, and can split commits at semantic boundaries.
Useful in local development, code review, and CI pipelines to enforce standardized messaging.

Quick Start

Analyze the current git diff --cached and generate a Conventional Commits compliant commit message.

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

To generate conventional commit messages from git diffs, you parse staged or unstaged outputs to determine type, scope, and subject. This formats your changes into standardized messages, reducing manual effort and ensuring consistent version-control history.

What is the best way to handle multiple semantic changes in a single staged git diff?▼

Handling multiple semantic changes in a staged git diff involves splitting commits at logical boundaries. The process proposes multiple conventional commit messages when needed, ensuring each distinct change receives an accurate, compliant commit message.

Can I use conventional commits generation in my CI pipelines?▼

Yes, you can use conventional commits generation in CI pipelines. The process parses git diff outputs to enforce standardized messaging workflows, automatically determining type, scope, and subject for each change without manual intervention.

Do I need to manually stage files before generating a conventional commit message?▼

You need staged files to generate a conventional commit message from local development. The process parses `git diff --cached` outputs, so you must stage your changes first to produce an accurate message with type and scope.

Does the conventional commit generator support breaking changes and footer lines?▼

The conventional commit generator supports breaking changes and footer lines. It formats messages following the Conventional Commits specification, automatically detecting and including optional breaking change notices and footer metadata in the output.