コミットメッセージの書き方ガイド

Generate emoji-enhanced Japanese Git commit messages from current diffs.

1|Updated Jan 25, 2022
One-click install
npx skills add https://github.com/Piory/dotfiles --skill -piory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: コミットメッセージの書き方ガイド
Source: https://github.com/Piory/dotfiles/tree/main/.codex/skills/commit-message
Command: npx skills add https://github.com/Piory/dotfiles --skill -piory

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you craft clear, context-aware Git commit messages by analyzing diffs and applying conventional commits with suitable emojis, reducing ambiguity in project history.

Core Features & Use Cases

  • Emoji-guided commits: Attach relevant emoji to reflect the change type.
  • Diff-driven messaging: Use git diff and status to tailor messages to actual changes.
  • Message segmentation: Split large changes into logical commits when appropriate.

Quick Start

Use the commit-message skill to examine the current changes and generate a commit message in Japanese that matches the Git Commit Guidelines, including an appropriate emoji. Then commit with: git commit -m "<your message>"

Frequently Asked Questions about コミットメッセージの書き方ガイド

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

FAQPage Schema
How do I write a commit message that follows Git conventions with emoji?

Commit messages with emoji categorize changes by type—fixes, features, docs, refactoring—making project history scannable and intent clear. This Skill analyzes your diffs and generates emoji-tagged messages that match Git Commit Guidelines, reducing ambiguity in version control history.

Can I generate commit messages automatically from git diff output?

Yes. This Skill examines git status and git diff to detect what changed, selects the appropriate emoji annotation based on the change type, and composes a structured commit message in Japanese that accurately reflects your modifications.

How do I split large changes into logical commits?

When multiple unrelated changes appear in a single diff, this Skill helps identify logical boundaries and generate separate commit messages for each segment, applying the right emoji to each so your repository history stays granular and reviewable.

What's the benefit of emoji in commit messages?

Emoji provide instant visual categorization—a glance shows whether a commit fixes a bug, adds a feature, or updates documentation. Combined with conventional commit structure, they accelerate code review, changelog generation, and historical navigation across large projects.

Do I need to understand Git Commit Guidelines before using this Skill?

No. This Skill encodes Git Commit Guidelines conventions internally, so you provide diffs and receive properly formatted messages without memorizing emoji mappings or conventions yourself.