commit-message

Generate Conventional Commits style commit messages with Japanese subjects.

Updated Sep 20, 2025
One-click install
npx skills add https://github.com/yellow-seed/crypto_wallet_tool --skill commit-message-yellow-seed
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-message
Source: https://github.com/yellow-seed/crypto_wallet_tool/tree/main/.github/skills/commit-message
Command: npx skills add https://github.com/yellow-seed/crypto_wallet_tool --skill commit-message-yellow-seed

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams standardize commit messages in Japanese using the Conventional Commits format, reducing ambiguity and improving traceability across the project history.

Core Features & Use Cases

  • Enforces Conventional Commits structure: requiring an English type and a Japanese subject, with optional body and footer to document changes.
  • Guided message construction: suggests succinct subjects and consistent formatting to improve readability.
  • Use Case: When preparing commits for features, fixes, documentation, or refactors across a Git repository to ensure uniform messages.

Quick Start

Provide an English type and a Japanese subject to generate a compliant commit message. Example: feat: 新規ログイン機能を追加

Frequently Asked Questions about commit-message

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

FAQPage Schema
How do I write Conventional Commits messages in Japanese?

Conventional Commits in Japanese combine an English type keyword (feat, fix, docs, refactor) with a concise Japanese subject line. This Skill generates properly formatted messages by accepting your type and Japanese description, then outputs a structured commit message that enforces the standard format with optional body and footer sections.

Why should my team use Conventional Commits for version control?

Conventional Commits standardize how changes are documented in Git history, reducing ambiguity and improving traceability. A structured format with English type and Japanese subject makes it easier to parse commit history, generate changelogs, and understand what changed and why across your project.

Can I use Conventional Commits for features, fixes, and documentation changes?

Yes. Conventional Commits apply across all change types—features, fixes, documentation updates, and refactors. This Skill supports all these types with the same structured format, ensuring consistency whether you're adding functionality, patching bugs, updating docs, or improving code structure.

What's the correct format for a Conventional Commit message with a Japanese subject?

The format is type: Japanese subject, where type is an English keyword like feat or fix. For example: feat: 新規ログイン機能を追加. The Skill enforces this structure and optionally appends body and footer sections for additional context and metadata.

Do I need special tools to enforce commit message standards on my Git repository?

This Skill generates compliant Conventional Commits messages directly. To enforce standards across your team, you'd typically pair generated messages with Git hooks or commit linters, but the Skill itself handles message construction and formatting validation.