skills.rest
InterfaceX-co-jp
InterfaceX-co-jpOFFICIAL
Explore all skills by this author →
WebsiteGitHub

genshijin-commit

Generate Conventional Commits-compliant commit messages with strict formatting constraints.

304|10|Updated Apr 6, 2026
Search Tags:#git#compression#code-review#commit-message#conventional-commits#breaking-change#issue-trailer
One-click install
npx skills add https://github.com/InterfaceX-co-jp/genshijin --skill genshijin-commit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: genshijin-commit
Source: https://github.com/InterfaceX-co-jp/genshijin/tree/main/skills/genshijin-commit
Command: npx skills add https://github.com/InterfaceX-co-jp/genshijin --skill genshijin-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

コミットメッセージ作成の手間とブレ（冗長・不統一）を減らし、履歴が読める形で「なぜ」を明確にした短いメッセージを素早く作ります。

Core Features & Use Cases

  • Conventional Commits準拠: type/scope/件名の型を守り、命令形で簡潔に要約します。
  • 「何を」より「なぜ」重視: 変更理由、破壊的変更、マイグレーション注意、関連Issue/PRなど必要時だけ本文を付けます。
  • 日英・圧縮ルール: 件名≤50文字目標、全体72文字折返し、末尾参照、禁止表現の排除で読みやすさと圧縮を両立します。

Quick Start

「/genshijin-commit で、ステージング中の変更に合うConventional Commits形式の超圧縮コミットメッセージを作って」と依頼してください。

Frequently Asked Questions about genshijin-commit

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

FAQPage Schema
How do I generate Conventional Commits messages that focus on why changes were made?▼

To generate Conventional Commits messages focused on intent, this Skill creates ultra-compressed messages that clearly communicate reasoning over implementation details, fitting feature, fix, and refactor scenarios.

What is the character limit for a Conventional Commits subject line and body wrapping?▼

Conventional Commits formatting constraints enforced here target a subject length of 50 characters or fewer, wrap the body at 72 characters, and eliminate prohibited phrases to ensure maximum readability.

How do I add breaking change notes and issue trailers to a git commit message?▼

You can include breaking change warnings, migration notes, and related issue or PR trailers as optional body details appended to the generated commit message.

Can I use this to create compressed commit messages for both Japanese and English?▼

Yes, this Skill applies Japanese and English compression rules, excluding prohibited expressions and enforcing strict type and scope formatting to maintain concise, readable git history.

What's the best way to automate commit message creation for staged git changes?▼

The best way to automate commit message creation is to request this Skill to analyze staged changes and output a strictly formatted, ultra-compressed Conventional Commits message.

When do I need a revert commit message versus a standard fix message?▼

A revert commit message is needed when undoing previous changes, while a standard fix message addresses bugs, both following the same Conventional Commits type and scope rules.

Related Skills

Explore More Software Engineering Skills→
mgoodman60mgoodman60

commit

Generate descriptive Git commit messages from repository changes with conventional formatting.

Community
Basic
mattg101mattg101
1

gcp-copy

Stage all changes, commit with a message, and push to a remote Git repository.

Community
Basic
YoshikemoloYoshikemolo
5

git-jira-integration

Generate Git branch names and validate commit messages against Jira issues.

Community
Intermediate
majiayu000majiayu000
258

git-commit-smart

Generate conventional commit messages from git diff output.

Community
Advanced