Automated summary
Analyses code changes and generates structured git commit messages with appropriate prefixes for clear, trackable version history.
Strengths
- Forces one commit per purpose, improving history readability.
- Provides clear prefix selection rules based on change type.
- Includes a pre-commit checklist to ensure quality.
- Produces consistent, well-formatted commit messages.
Limitations
- Requires discipline to avoid mixing unrelated changes.
- May not fit projects with different commit conventions.
- Depends on accurate staging for optimal use.
Use this skill when you want to maintain a clean, conventional git history with meaningful commit messages.
Avoid using it during rapid prototyping where commit quality is not a priority, or if your team uses a different commit convention.
Security analysis
SafeThe skill uses only standard git commands (status, diff, add, commit) for analyzing changes and creating commits. There are no destructive, network, or data exfiltration operations. It does not instruct the AI to run untrusted code or expose secrets.
No concerns found
How this analysis is madeExamples
/git-commit Commit the current staged changes with an appropriate prefix./git-commit I have unstaged changes in multiple files. Help me decide how to split them into logical commits and commit each./git-commit Review the current diff and create a well-structured commit message.name: git-commit description: Gitコミット時に変更内容を分析し、コミットprefix（add/fix/docs/refactor/test/chore/perf/build/ci/revert/style）を適切に選定して、明確で追跡可能なコミットメッセージを作成・実行するためのスキル。コミットメッセージ作成、prefix選定、複数変更の分割判断、コミット実行時に使用する。 allowed-tools: Read, Write, Bash
Git Commit スキル
変更差分を根拠に、適切な prefix を決定して高品質なコミットを作るためのスキルです。
このスキルで採用するprefix
add: ユーザー価値が増える機能追加・仕様追加fix: バグ修正・不具合是正docs: ドキュメントのみ変更refactor: 振る舞いを変えない内部改善test: テスト追加・修正chore: 雑務的変更（設定、依存更新、軽微保守）perf: パフォーマンス改善build: ビルドシステムや依存解決の変更ci: CI/CD設定の変更revert: 既存コミットの取り消しstyle: フォーマットやlintのみ（意味的変更なし）
基本方針
- 1コミット1目的を守る
- コミット前に差分を確認する
- コミットメッセージは日本語で記述する
prefixは「変更の主目的」で決める- 迷う場合の優先順位は
fix > add > refactor > chore
メッセージ形式
<prefix>: <summary>
<detail>
- <file path 1>
- <file path 2>
summaryは 30〜60 文字目安detailは 1〜3 行で要点のみ記載- 修正ファイル名は本文に含めてよい（簡潔に列挙）
例:
add: 記事選定ロジックに重複除外ルールを追加
候補記事の重複判定を導入し、配信品質を安定化。
- src/newsletter/selector.py
- tests/test_selector.py
fix: タイムアウト時に再試行回数が増えない不具合を修正
リトライカウンタ更新条件の分岐漏れを修正。
- src/lambda/handler.py
```text` docs: ローカル実行手順と環境変数の説明を更新
READMEの手順を最新構成に合わせて整理。
- README.md
## 実行フロー
1. 変更確認
```bash
git status --short
git diff --staged
git diff
- 変更の主目的を1文で定義
- 「何を直した/追加したか」ではなく「なぜ必要か」を明確化
- prefix判定
- 判定表に従い最も影響の大きい変更を採用
- 複数目的が混在する場合はコミット分割を優先
- ステージング整理
git add <file>
# または
git add -p
- コミット実行
git commit -m "<prefix>: <summary>" -m "<detail>\n- <file path>"
prefix判定ルール（実務用）
- バグを直しているなら
fix（新規機能を含んでも原則fix） - 新しい振る舞いを導入するなら
add - 外部仕様に影響せず内部構造のみ整理なら
refactor - テストだけなら
test - ドキュメントだけなら
docs - CI定義だけなら
ci - 依存解決・ビルド定義中心なら
build - 速度改善が主目的なら
perf - どれにも当てはまらない保守作業は
chore
NG例
update,misc,changesのような曖昧なsummary- 無関係な変更を1コミットに混在
fixなのに本文が「機能追加」中心- 巨大コミットを分割せずにそのまま記録
- 詳細が長すぎて差分を読まないと要点が分からない本文
実行前チェックリスト
- 差分を確認した
- prefixの根拠を説明できる
- 1コミット1目的になっている
- summary と detail が重複せず簡潔
- 本文に主要な修正ファイル名を記載した
- テストまたは最低限の動作確認を実施した
クイックコマンド
このスキルを呼び出すコマンドprefixは以下を推奨:
/git-commit
実行例:
/git-commit 「変更差分を見て適切なprefixでコミットして」
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 filesThis 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.mdFrom the root of a test project, save the file as .skill-downloads/git-commit-with-prefix-mm78nns6/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/git-commit-with-prefix-mm78nns6' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/git-commit-with-prefix-mm78nns6/download' --output '.skill-downloads/git-commit-with-prefix-mm78nns6/SKILL.md.part' && mv '.skill-downloads/git-commit-with-prefix-mm78nns6/SKILL.md.part' '.skill-downloads/git-commit-with-prefix-mm78nns6/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.
Tools declared by the author (check availability in your agent): Read, Write, Bash
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/git-commit-with-prefix-mm78nns6/SKILL.md' && test -s '.skill-downloads/git-commit-with-prefix-mm78nns6/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/git-commit' && cp -R '.skill-downloads/git-commit-with-prefix-mm78nns6' '.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 installationopenskills install './.skill-downloads/git-commit-with-prefix-mm78nns6'openskills read 'git-commit-with-prefix-mm78nns6'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 syncManual 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/git-commit-with-prefix-mm78nns6/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.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
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.
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.