skills.rest
kamijodev
kamijodevCOMMUNITY
Explore all skills by this author →
GitHub

git-commit

Generate Japanese Conventional Commits v1.0.0 messages from staged Git diffs.

Updated Aug 27, 2026
Search Tags:#git#developer tools#code review#version control#commit#conventional commits
One-click install
npx skills add https://github.com/kamijodev/dotfiles --skill git-commit-kamijodev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/kamijodev/dotfiles/tree/main/dot_claude/skills/git-commit
Command: npx skills add https://github.com/kamijodev/dotfiles --skill git-commit-kamijodev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of well-structured, Conventional Commits messages, ensuring consistency and clarity in your project's version history.

Core Features & Use Cases

  • Automated Message Generation: Analyzes git diff to suggest meaningful commit messages.
  • Conventional Commits Compliance: Adheres to the v1.0.0 specification for type, scope, description, body, and footers.
  • Use Case: After making code changes, simply ask the AI to "commit my changes," and it will generate a compliant commit message based on your diff, then execute the commit.

Quick Start

Ask the AI to commit your staged changes.

Frequently Asked Questions about git-commit

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

FAQPage Schema
How do I generate conventional commits from staged git diffs?▼

To generate conventional commits from staged git diffs, this Skill analyzes your code changes to determine the type, scope, and description, then automatically executes the git commit command with a compliant message.

What happens if I try to commit with no staged changes?▼

If there are no staged changes, the commit process pauses and prompts you to stage files first, ensuring the generated conventional commit message accurately reflects actual code diffs.

Can I automate Japanese commit messages for version control?▼

Yes, you can automate Japanese commit messages for version control by asking the AI to commit changes, which analyzes the staged diff and outputs a Conventional Commits v1.0.0 compliant message in Japanese.

Does the conventional commit message include scope and body details?▼

The conventional commit message includes scope and body details by analyzing the git diff to construct a fully compliant v1.0.0 message structure with appropriate type, scope, description, and footers.

What is the best way to maintain consistent git commit history?▼

The best way to maintain consistent git commit history is automating message generation from staged diffs, which enforces Conventional Commits v1.0.0 specification compliance for clarity and structure across your project.

Related Skills

Explore More Software Engineering Skills→
voidrotvoidrot

git-commit

Generates Conventional Commits compliant Git commit messages from staged file diffs.

Community
Advanced
timzaaktimzaak
64

t-release

Automate version bumps, release tagging, and pushing release commits to git remotes.

Community
Intermediate
greyhaven-aigreyhaven-ai
29

grey-haven-linear-workflow

Automate Linear issue creation, branch naming, and PR integration with Git workflows.

Community
Basic
itsjaviitsjavi
1

generate-commit-msg

Generate Conventional Commit messages from staged Git changes.

Community
Basic