git-commit-message
Use when the user asks for a git commit message or semantic commit guidance. Produce one semantic commit message that prioritizes stated intent and effect and stays consistent with the described change.
Best use case
git-commit-message is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Use when the user asks for a git commit message or semantic commit guidance. Produce one semantic commit message that prioritizes stated intent and effect and stays consistent with the described change.
Teams using git-commit-message should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/git-commit-message/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How git-commit-message Compares
| Feature / Agent | git-commit-message | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Use when the user asks for a git commit message or semantic commit guidance. Produce one semantic commit message that prioritizes stated intent and effect and stays consistent with the described change.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Git Commit Message Generate one semantic commit message that captures the change at the right level: intent and effect first, details second. ## Response Contract - One recommended commit message. - One sentence explaining the chosen type, scope, and summary. ## Message Model ### Default format `<type>(<scope>): <summary>` Omit `(scope)` when it does not add signal. ### Components - **Type**: the change class. - **Scope**: the primary area changed, when it improves precision. - **Summary**: a short statement of intent and effect. ## Standards Apply these standards throughout the suggestion. Each standard is single-sourced here and referenced elsewhere by its ID. - **format.default — Default format** Use the default format and omit scope when it is unclear or low-signal. - **type.minimal — Minimal accurate type** Choose the smallest type that fits the change: `feat`, `fix`, `chore`, `refactor`, `docs`, `test`, `perf`. - **scope.signal — Scope adds signal** Use a narrow, stable scope that names the main area changed. Avoid repeating obvious repo or product context. - **summary.intent_effect — Intent and effect first** Prefer the user’s stated intent and the observable effect of the change over mechanical descriptions of edits. - **signal.dense — Dense and non-redundant** Keep `type`, `scope`, and `summary` complementary. Avoid overlap and embellishment. ## Workflow 1. Extract the user’s stated intent, the change’s effect, and the primary area. 2. Select type. Apply `type.minimal`. 3. Select scope only if it adds precision. Apply `scope.signal`, `format.default`. 4. Write a concise summary focused on intent and effect. Apply `summary.intent_effect`, `signal.dense`. 5. Emit the final message per the Response Contract. ## Acceptance Criteria A revision is complete only if all checks pass. - **Response**: Output satisfies the Response Contract. - **Standards satisfied**: `format.default`, `type.minimal`, `scope.signal`, `summary.intent_effect`, `signal.dense`.
Related Skills
github-commit
Create a well-formatted git commit following best practices
git-create-commit-skill
Use when creating git commits - mandates commits format with required scopes for all new commits, provides scope discovery from codebase structure, and prevents rationalization under pressure (emergency, fatigue, ambiguity)
git-commit
Stage and commit git changes with conventional commit messages. Use when user wants to commit changes, or asks to save their work, even when committing your own work after completing a task. Also activates when user says "commit changes", simply "commit", or similar git workflow requests. Never commit without loading this skill.
git-commit-push
Guidelines for creating AI-generated Git commits with proper format and attribution
git-auto-commit
현재 저장소의 변경사항을 분석해 한국어 커밋 메시지(MMDD:HHmm - 요약)와 상세 변경 요약을 생성하고, `yarn lint` 및 `yarn build`를 모두 통과한 뒤 전체 스테이징 후 커밋합니다(푸시 없음). lint/build 실패 시 AI가 로그를 기반으로 자동 수정→재시도를 수행합니다(최대 N회). 기본 브랜치는 develop이며, 다른 브랜치에서는 경고 후 진행합니다.
conventional-commits
Writes and reviews Conventional Commits commit messages (v1.0.0) to support semantic versioning and automated changelogs. Use when drafting git commit messages, PR titles, release notes, or when enforcing a conventional commit format (type(scope): subject, BREAKING CHANGE, footers, revert).
Conventional Commit Generator
This skill should be used when the user asks to "create a conventional commit", "generate conventional commits", "commit with conventional format", "group my changes for commits", "make a conventional commit message", or mentions "semantic commits", "commitizen", "commit conventions". Analyzes staged and unstaged changes, groups related modifications, and generates properly formatted conventional commit messages with interactive commit grouping options.
committing-staged-with-message
Generate commit message for staged changes, pause for approval, then commit. Stage files first with `git add`, then run this skill.
commit
現在の変更をgit commitする。変更内容を分析し、適切なコミットメッセージを自動生成してコミットを作成する。
commit-validator
Validates commit messages against Conventional Commits specification using programmatic validation. Replaces the git-conventional-commit-messages text file with a tool that provides instant feedback.
safe-commit
⚠️ MANDATORY - YOU MUST invoke this skill when committing. Complete commit workflow with all safety checks. Invokes security-scan, quality-check, and run-tests skills. Shows diff, gets user approval, creates commit with conventional format. NO AI attribution. User approval REQUIRED except during PR creation. NEVER commit manually.
message-authentication-code-pattern
Security pattern for implementing Message Authentication Codes (MACs) to ensure data integrity and origin authentication. Use when implementing HMAC, CMAC, or other MAC algorithms, verifying message integrity, authenticating message origin with shared secrets, or when non-repudiation is NOT required. Specialization of Cryptographic action pattern.