conventional-commit

Generates Japanese Conventional Commit messages and executes git commits for detected repository changes.

Updated Jan 17, 2026

Search Tags:#automation #git #japanese #developer-workflow #commit-message #conventional-commit #diff-analysis

Ready to run

npx skills add https://github.com/inakam/dotfiles-raspberry --skill conventional-commit-inakam

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developers often spend time crafting clear, consistent commit messages and deciding how to split changes into logical commits, especially when following Conventional Commits in Japanese, which leads to inconsistent history and review friction.

Core Features & Use Cases

Change detection and analysis: Inspect git status and diffs to identify modified files and summarize changes.
Message generation: Produce Conventional Commits formatted commit messages in Japanese, including suggested types and scopes.
Interactive commit workflow: Present commit groupings and messages for user confirmation, then run git add and git commit for approved commits.
Use case: After finishing a set of edits, invoke the skill to produce review-friendly, convention-compliant Japanese commit messages and apply them automatically.

Quick Start

Ask the skill to analyze the current repository changes, propose Japanese Conventional Commit messages grouped by logical changes, and apply them after you confirm each suggestion.

Frequently Asked Questions about conventional-commit

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

FAQPage Schema

How do I auto-generate Japanese conventional commit messages from git diffs?▼

Yes, you can group multiple file changes into separate logical commits. The Skill inspects git status and diffs to identify modified files, then proposes grouped conventional commit messages in Japanese for your confirmation.

How does this commit workflow handle user approval before applying changes?▼

The commit workflow handles user approval by presenting suggested commit groupings and Japanese conventional commit messages interactively, then running git add and git commit only after you explicitly confirm each proposal.

Does this tool require any external dependencies to format Japanese commit messages?▼

No external dependencies are required. The Skill operates directly within your local git repository to analyze diffs and execute commits using conventional commits formatting in Japanese.

What is the best way to maintain consistent conventional commit history in a Japanese development workflow?▼

The best way to maintain consistent conventional commit history is an automated workflow that analyzes repository changes and enforces conventional commits formatting in Japanese, reducing review friction and inconsistent messaging.

Can I use this to split uncommitted changes into multiple logical git commits?▼

Yes, you can split uncommitted changes into logical git commits. The Skill detects repository changes via git status and git diff, summarizes modifications, and groups them into separate conventional commit proposals for interactive execution.