git-commit

Generate Conventional Commits messages from git diffs in English or Japanese.

1|Updated Jun 10, 2016
One-click install
npx skills add https://github.com/yykamei/dotfiles --skill git-commit-yykamei
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/yykamei/dotfiles/tree/main/.config/opencode/skills/git-commit
Command: npx skills add https://github.com/yykamei/dotfiles --skill git-commit-yykamei

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you write professional, standardized Git commit messages that clearly communicate the purpose and impact of your code changes.

Core Features & Use Cases

  • Standardized Format: Enforces Conventional Commits structure (type, subject, body).
  • Language Adaptability: Supports both English and Japanese commit messages with specific style rules.
  • Use Case: Ensure all team members contribute consistent and informative commit messages, improving code review efficiency and project history readability.

Quick Start

Use the git-commit skill to generate a commit message for the provided git diff.

Frequently Asked Questions about git-commit

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

FAQPage Schema
How do I generate a Git commit message from a diff?

You can generate Conventional Commits messages by providing a git diff, which the skill analyzes to create a structured message with type, subject, and body explaining the rationale behind the code changes.

What is the Conventional Commits format for version control?

Conventional Commits format structures version control messages into a type, subject, and body, ensuring clarity and consistency by focusing on the 'why' behind code changes rather than just the 'what'.

Can I write Conventional Commits in Japanese?

Yes, you can generate Conventional Commits in Japanese, as the skill supports both English and Japanese languages with specific style rules to maintain formatting consistency in version control.

Does this Git commit generator require any specific dependencies?

No, this Git commit generator does not require any specific dependencies, allowing you to directly analyze git diffs and craft standardized messages without additional environment setup.

Why focus on the 'why' in a commit message?

Focusing on the 'why' in a commit message improves code review efficiency and project history readability by explaining the purpose and impact of changes rather than just listing the modified code.

What is the best way to standardize team Git commit messages?

The best way to standardize team Git commit messages is to enforce the Conventional Commits structure, ensuring all members contribute consistent, informative messages that clearly communicate code change impacts.