commit-message
Format git commit messages combining Conventional Commits summary lines with Linux kernel-style bodies. Use when writing, reviewing, or formatting commit messages.
Best use case
commit-message is best used when you need a repeatable AI agent workflow instead of a one-off prompt. It is especially useful for teams working in multi. Format git commit messages combining Conventional Commits summary lines with Linux kernel-style bodies. Use when writing, reviewing, or formatting commit messages.
Format git commit messages combining Conventional Commits summary lines with Linux kernel-style bodies. Use when writing, reviewing, or formatting commit messages.
Users should expect a more consistent workflow output, faster repeated execution, and less time spent rewriting prompts from scratch.
Practical example
Example input
Use the "commit-message" skill to help with this workflow task. Context: Format git commit messages combining Conventional Commits summary lines with Linux kernel-style bodies. Use when writing, reviewing, or formatting commit messages.
Example output
A structured workflow result with clearer steps, more consistent formatting, and an output that is easier to reuse in the next run.
When to use this skill
- Use this skill when you want a reusable workflow rather than writing the same prompt again and again.
When not to use this skill
- Do not use this when you only need a one-off answer and do not need a reusable workflow.
- Do not use it if you cannot install or maintain the related files, repository context, or supporting tools.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/commit-message/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How commit-message Compares
| Feature / Agent | 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?
Format git commit messages combining Conventional Commits summary lines with Linux kernel-style bodies. Use when writing, reviewing, or formatting commit messages.
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
# Commit Message Formatting
## Summary Line
Use Conventional Commits format:
```
<type>(<scope>): <description>
```
- **type** (required): `feat`, `fix`, `docs`, `style`, `refactor`, `perf`, `test`, `build`, `ci`, `chore`
- **scope** (optional): component or area affected, in parentheses
- **description**: imperative mood, lowercase start, no period, max 50 chars (hard limit 72)
- For breaking changes: add `!` before colon: `feat(api)!: remove deprecated endpoint`
## Body
Separate from summary with blank line. Follow kernel style:
- Wrap at 72 columns
- Imperative mood ("Add feature" not "Added feature")
- Explain **why**, not what (the diff shows what)
- Describe user-visible impact and motivation
- Quantify improvements with numbers when applicable
When referencing commits, use 12+ char SHA with summary:
```
Commit e21d2170f36602ae2708 ("video: remove unnecessary
platform_set_drvdata()") introduced a regression...
```
## No Trailers
Omit all trailers: no `Signed-off-by`, `Reviewed-by`, `Acked-by`, `Tested-by`, `Cc`, `Fixes`, `Link`, etc.
## Examples
Single-line fix:
```
fix(parser): handle empty input without panic
```
Feature with body:
```
feat(auth): add OAuth2 PKCE flow support
Mobile and SPA clients cannot securely store client secrets. PKCE
allows these clients to authenticate safely without exposing
credentials in client-side code.
This reduces authentication failures for mobile users by eliminating
the insecure implicit flow workaround.
```
Breaking change:
```
feat(api)!: require authentication for all endpoints
Anonymous access created security vulnerabilities and complicated
rate limiting. Requiring auth simplifies the security model and
enables per-user quotas.
Clients must now include a valid Bearer token with every request.
```
Refactor:
```
refactor(db): extract connection pooling into dedicated module
The monolithic database module grew to 2000+ lines, making
maintenance difficult. Separating connection pooling improves
testability and allows independent configuration tuning.
```Related Skills
commit-work
Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits). Use when the user asks to commit, craft a commit message, stage changes, or split work into multiple commits.
caveman-commit
Ultra-compressed commit message generator. Cuts noise from commit messages while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious. Use when user says "write a commit", "commit message", "generate commit", "/commit", or invokes /caveman-commit. Auto-triggers when staging changes.
backend-atomic-commit
Pedantic backend pre-commit and atomic commit Skill for Django/Optimo-style repos. Enforces local AGENTS.md / CLAUDE.md, pre-commit hooks, .security/* helpers, and Monty’s backend engineering taste – with no AI signatures in commit messages.
commit-message-generator
Generate appropriate commit messages based on Git diffs
making-commits
Guidelines on makign git commits
pre-commit-check
コミット前品質チェックスキル（Lint、テスト、ビルドの高速検証）
managing-commits
Git commit quality and conventional commits expertise with automatic issue tracking integration. Auto-invokes when the user explicitly asks about commit message format, commit quality, conventional commits, commit history analysis, issue references in commits, or requests help writing commit messages. Integrates with the issue cache for automatic issue references.
commit-helper
Expert conventional commits assistant for the Logseq Template Graph project. Analyzes git changes and generates proper conventional commit messages with correct type, scope, and format. Use when the user needs help writing commits or validating commit messages.
commit-prepare
Prepare git commit messages following conventional commits. Activates on: commit, prepare commit, commit this, commit message, ready to commit, stage and commit
high-quality-commit
コード変更を適切なgitコミット戦略でgit commitします。基本的には既存のgitコミットへのsquash戦略を採用し、必要に応じてブランチ全体のgitコミット履歴を再構成します。実装完了時やユーザーがgit commitを依頼した時に使用します。
draft-commit
Create a thoughtful, supportive commit message from your staged changes.
commit-drafter
Automatically draft commit messages by analyzing git status and staged changes