Skills Guide

Conventional Git Commit

VerifiedSafe

Create Git commits with conventional commit messages in Japanese, focusing on what was solved.

Download and use
Sby Skills Guide Bot
DevelopmentIntermediate
7/22/2026
Claude Code
#git#conventional-commits#commit-messages#version-control#workflow

Recommended for

Backend developerClaude CodeCode reviewFrontend developerFullstack developerRefactoring

Automated summary

Reviews a Git repository's changes, checks recent history, and creates commits in Conventional Commits format with Japanese messages that describe the problem being solved.

Strengths

  • Enforces a clear Conventional Commits format with a type table and good/bad examples
  • Reads the last 20 commits to match existing style while suggesting better phrasing
  • Splits work into commits based on plan/TODO steps or logical units (fix, feature, refactor)
  • Includes safeguards: diff review, avoiding secrets, caution with --amend and breaking changes

Limitations

  • Commit messages are Japanese-only, which does not suit teams requiring English
  • Plan-based splitting depends on Claude Code-specific features (TodoWrite, develop:read-todo skill)
  • Always appends a Co-Authored-By: Claude trailer, which some teams reject
When to use it

Use it when you want changes committed with structured Japanese Conventional Commits messages.

When not to use it

Avoid it if your project requires English messages or a different convention such as Gitmoji or ticket prefixes.

Security analysis

Safe
Quality score88/100

The skill only uses standard git inspection and commit commands (git status/diff/log/add/commit). There is no destructive command, no network exfiltration, no obfuscated payload, and no disabling of safety. It actively instructs the agent to avoid committing .env/credential files, to commit only when explicitly requested, to use --amend only for unpushed self-made commits, and to confirm before breaking changes—all sound guardrails.

No concerns found

How this analysis is made

Examples

Commit current changes
変更をコミットして
Commit per TODO step
TODOのステップごとに分けてコミットして
Split fix and feature
Review my working tree, commit the bug fix separately from the new feature, and use Conventional Commits in Japanese

name: git-commit description: Git リポジトリへの変更をコミットする。Conventional Commits 形式で日本語のコミットメッセージを作成する。過去の履歴を参考にしつつ、「何を解決したか」を明確に記述する。TODO/計画がある場合はそのステップ単位でコミットを分割する。ユーザーが「コミットして」「変更をコミット」「/commit」「git commit」などと言ったときに使用する。

Git Commit

変更内容を確認し、Conventional Commits 形式でコミットを作成する。

コミットメッセージのルール

  • 言語: 日本語
  • スコープ: 機能名を使用（auth, api, ui, db など）
  • 内容: 「何をしたか」ではなく「何を解決したか」を書く

形式:

<type>(scope): <description>

[optional body]

Co-Authored-By: Claude <noreply@anthropic.com>

良い例・悪い例:

# NG: 何をしたか（実装の説明）
fix(auth): validateUser関数を修正
feat(ui): ボタンコンポーネントを追加

# OK: 何を解決したか（目的・価値の説明）
fix(auth): 無効なトークンでもログインできてしまう問題を修正
feat(ui): ユーザーが直感的に操作を完了できるようCTAボタンを追加

タイプ一覧: | タイプ | 用途 | |--------|------| | feat | 新機能 | | fix | バグ修正 | | docs | ドキュメント | | style | フォーマット（動作に影響なし） | | refactor | リファクタリング | | perf | パフォーマンス改善 | | test | テスト | | build | ビルド設定 | | ci | CI設定 | | chore | その他 |

詳細は references/conventional-commits.md を参照。

コミット粒度

TODO/計画がある場合

以下を確認し、各ステップを1コミット単位とする：

  • TodoWrite のタスクリスト: 現在のセッションで管理しているタスク
  • develop:read-todo スキル: プロジェクトの TODO ファイル

計画がない場合

以下の基準で論理的に分割：

  • 機能追加・バグ修正・リファクタリングは別コミット
  • 関連するファイル群を1コミットにまとめる
  • 独立して意味を持つ変更単位で分割

分割の例:

# 例: 機能追加とバグ修正が混在している場合

# 1. まずバグ修正をコミット
git add <bug-fix-files>
git commit -m "fix(auth): 無効なトークンでログインできる脆弱性を修正"

# 2. 次に機能追加をコミット
git add <feature-files>
git commit -m "feat(auth): パスワード忘れ時に自己解決できるようリセット機能を追加"

ワークフロー

1. 状態確認

git status
git diff --staged
git diff

2. 過去履歴の確認

git log --oneline -20

過去のコミットメッセージのスタイル（言語、スコープの付け方、記述の粒度）を確認し、参考にする。ただし、より良い表現があれば提案する。

3. TODO/計画の確認

  • TodoWrite のタスクリストを確認
  • develop:read-todo スキルで TODO ファイルを確認
  • 計画がある場合、どのステップに対応する変更かを特定

4. コミット単位の設計

差分を確認し、以下を特定：

  • 変更の種類（新機能、バグ修正、リファクタリング等）
  • 影響範囲（スコープ）→ 機能名を使用
  • 破壊的変更の有無
  • コミットの分割方法（計画ステップ or 論理的単位）

5. 各コミットのステージング＆実行

# ステージング
git add <files>

# コミット（HEREDOCで複数行対応）
git commit -m "$(cat <<'EOF'
<type>(scope): <何を解決したか>

Co-Authored-By: Claude <noreply@anthropic.com>
EOF
)"

6. コミット後の確認

git log --oneline -3
git status

注意事項

  • コミット前に必ず git diff で変更内容を確認する
  • .env や認証情報を含むファイルをコミットしない
  • コミットは明示的にユーザーから依頼された場合のみ実行する
  • --amend は直前のコミットが自分で作成し、まだプッシュしていない場合のみ使用可能
  • 破壊的変更がある場合はタイプの後に ! を付ける（例: feat!:）。ただし、! を付ける前に必ずユーザーに確認する

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/conventional-git-commit-mrwaka2f/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/conventional-git-commit-mrwaka2f' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/conventional-git-commit-mrwaka2f/download' --output '.skill-downloads/conventional-git-commit-mrwaka2f/SKILL.md.part' && mv '.skill-downloads/conventional-git-commit-mrwaka2f/SKILL.md.part' '.skill-downloads/conventional-git-commit-mrwaka2f/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/conventional-git-commit-mrwaka2f/SKILL.md' && test -s '.skill-downloads/conventional-git-commit-mrwaka2f/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/git-commit' && cp -R '.skill-downloads/conventional-git-commit-mrwaka2f' '.claude/skills/git-commit'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/conventional-git-commit-mrwaka2f'

openskills read 'conventional-git-commit-mrwaka2f'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/conventional-git-commit-mrwaka2f/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills

React Hook Form Best Practices

Development

Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.

Claude CodeCursorWindsurf+2intermediateSafe 108,623
Skills Guide Bot

Emotion to Mantine Migration

Development

Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.

Claude CodeCursorWindsurf+1intermediateSafe 48,981
Skills Guide Bot

Scope Creep Detector

Development

Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.

Claude CodeCursorCodexintermediateSafe 135,015
Skills Guide Bot