skills.rest
yellow-seed
yellow-seedCOMMUNITY
Explore all skills by this author →
GitHub

commit-message

Generates Conventional Commits format commit messages with Japanese subjects and bodies.

1|Updated Feb 16, 2025
Search Tags:#git#changelog#version control#conventional commits#japanese#commit message#git commit
One-click install
npx skills add https://github.com/yellow-seed/my-portfolio --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/my-portfolio/tree/main/.github/skills/commit-message
Command: npx skills add https://github.com/yellow-seed/my-portfolio --skill commit-message-yellow-seed

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing consistent, well-structured commit messages is tedious and often inconsistent across a project. This Skill standardizes commit creation by generating Conventional Commits format messages with Japanese subjects and bodies, complete with issue references and required signatures. ## Core Features & Use Cases - Conventional Commits Formatting: Enforces the type/subject/body/footer structure with eight defined types (feat, fix, docs, style, refactor, perf, test, chore). - Japanese Message Rules: Applies strict writing rules including 50-character subject limits, imperative mood, and 72-character body wrapping. - Issue Linking and Signatures: Automatically appends Closes #N references, BREAKING CHANGE footers, and the mandatory Claude Code signature block. - Use Case: After staging changes with git, ask for a commit and receive a properly formatted message like "feat: Docker Composeとuvによる開発環境をセットアップ" with a detailed bulleted body and issue reference, ready to execute via HEREDOC. ## Quick Start Review my staged changes with git status and git diff, then create a commit with a properly formatted Conventional Commits message in Japanese.

Frequently Asked Questions about commit-message

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

FAQPage Schema
How do I write a Conventional Commits message in Japanese?▼

Use the format type: subject, where type is English (feat, fix, docs, etc.) and the subject is Japanese under 50 characters in imperative form. Add an optional Japanese body wrapped at 72 characters and a footer with issue references like Closes #123.

What commit types are available in Conventional Commits?▼

This Skill supports eight types: feat for new features, fix for bug fixes, docs for documentation, style for formatting, refactor for code restructuring, perf for performance, test for test changes, and chore for build or tooling updates.

How do I reference an issue in a git commit message?▼

Add a footer line with Closes #123 to link and auto-close the issue. For breaking changes, include a BREAKING CHANGE: footer with a Japanese explanation of the impact.

Why should commit messages use HEREDOC in git commands?▼

HEREDOC preserves multi-line formatting, bullet points, and special characters in commit messages without shell escaping issues. It ensures the subject, body, footer, and signature blocks are committed exactly as written.

What are the subject line rules for Conventional Commits?▼

The subject must be in Japanese, under 50 characters, written in imperative form, start with a lowercase character, and have no trailing period. It should concisely summarize what the change does.

Related Skills

Explore More Software Engineering Skills→
ss49919201ss49919201

git-add-commit

Stage git changes and generate commit messages from diffs.

Community
Basic
santychuycomsantychuycom

ship

Analyze diffs, create atomic conventional commits, push, and open pull requests.

Official
Advanced
owenlamontowenlamont
1

python-lint-format

Automate Python code linting and formatting with pre-commit hooks.

Community
Advanced
mjbellantonimjbellantoni

squash-merge

Draft standardized commit messages and squash merge GitHub pull requests via gh CLI.

Community
Intermediate