commit-helper

Generate Conventional Commits compliant messages from git diffs.

Updated Aug 27, 2026

Search Tags:#automation #git workflow #conventional commits #commit messages

One-click install

npx skills add https://github.com/ShunsukeHayashi/Miyabi --skill commit-helper-shunsukehayashi

Or copy as Structured Prompt for Agent▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires Bash, Read, Grep, and includes scripts (resource) components.

What problem does it solve?

This Skill eliminates the tedious work of writing commit messages by automatically generating Conventional Commits compliant messages from git diffs.

Quick Start

Generate a commit message for the changes in 'src/auth/' following Conventional Commits format.

Frequently Asked Questions about commit-helper

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

FAQPage Schema

How do I generate conventional commit messages automatically from git diffs?▼

Conventional commits are automatically generated from your git diffs, applying formatting rules for commit type (feat, fix, docs, style, refactor, perf, test, chore, ci), enforcing imperative subject lines under 50 characters, and optionally adding body and footer sections with breaking changes and issue references.

Can I use conventional commits to standardize commit messages across my repositories?▼

Yes. Conventional commits enforce consistent formatting across repositories and CI workflows by automatically generating messages that follow the spec, eliminating manual formatting work during commit creation and staging reviews.

What's the best way to enforce commit message formatting in git workflows?▼

Conventional commits enforce formatting automatically during commit creation by generating messages that comply with the spec, including proper type classification, imperative mood, character limits, and optional breaking change and issue closure sections.

Do I need to manually write commit message bodies and footers?▼

No. The tool optionally emits body and footer sections automatically, including breaking changes and closes references, so you can draft complete messages without manual formatting.

Can conventional commits work with CI workflows and automated deployments?▼

Yes. Conventional commits apply across repositories and CI workflows, generating compliant messages during commit creation and staging reviews to maintain formatting consistency in automated pipelines.