skills.rest
kazuho39
kazuho39COMMUNITY
Explore all skills by this author →
GitHub

commit-message

Generate Git commit messages from staged changes with rule-based prefixes.

Updated Aug 23, 2026
Search Tags:#automation#git#developer tools#git workflow#conventional commits#commit message
One-click install
npx skills add https://github.com/kazuho39/kzo-document --skill commit-message-kazuho39
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit-message
Source: https://github.com/kazuho39/kzo-document/tree/main/.github/skills/commit-message
Command: npx skills add https://github.com/kazuho39/kzo-document --skill commit-message-kazuho39

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of Git commit messages, ensuring consistency and adherence to project-specific rules, thereby improving the clarity and maintainability of your commit history.

Core Features & Use Cases

  • Automated Message Generation: Analyzes staged Git changes to suggest appropriate commit messages.
  • Rule-Based Prefixes: Applies prefixes like add:, update:, dev:, and chore: based on the nature of the changes.
  • Japanese Language Support: Generates concise commit messages in Japanese.
  • Use Case: Before committing code, you can ask this Skill to generate a commit message based on your staged changes, ensuring it follows the project's established conventions for new features, updates, or maintenance tasks.

Quick Start

Use the commit-message skill to generate a git commit message for the staged changes.

Frequently Asked Questions about commit-message

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

FAQPage Schema
How do I generate a Git commit message based on staged changes?▼

You can generate a Git commit message by asking this Skill to analyze your staged changes. It identifies file modifications and applies rule-based prefixes like add:, update:, dev:, and chore: to produce a concise, convention-compliant message.

What is the best way to automate Japanese commit messages for VitePress documentation?▼

Automating Japanese commit messages for VitePress is handled by analyzing staged Git changes and applying prefixes such as add: and chore:. This ensures your documentation site development workflow maintains a consistent, rule-based commit history.

Can I use conventional commit prefixes like add and update for my git workflow?▼

Yes, this Skill supports your git workflow by applying specific rule-based prefixes including add:, update:, dev:, and chore:. It evaluates your staged file modifications to select the appropriate prefix and generates a matching commit message.

Does this commit message generator support custom project-specific rules?▼

This commit message generator follows project-specific rules to ensure consistency and maintainability. It analyzes file types and modifications to apply appropriate prefixes, specifically supporting established conventions for new features, updates, or maintenance tasks.

What are the limitations when generating commit messages with this approach?▼

A limitation is that the generated commit messages follow Japanese language conventions and specific prefixes like add: and dev:, which may not suit projects requiring English descriptions or standard conventional commits like feat: or fix:.

Related Skills

Explore More Software Engineering Skills→
yoshihiko555yoshihiko555

commit

Stage and commit only files discussed in the conversation.

Community
Advanced
wewetv1987-cellwewetv1987-cell

git-helper

Manage Git repository status, pull, push, branch, and log operations.

Community
Basic
a3taia3tai
35

docs-design

Analyze and adjust layout, colors, typography, and components in VitePress documentation sites.

Official
Intermediate
masutakamasutaka
10

suggest-commit-message

Generate semantic Git commit messages from `git diff HEAD` in English or Japanese.

Community
Intermediate