How do I install the Commit Messages skill?

Run npx skillmds@latest add comeonoliver/commit-messages in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Commit Messages skill do?

Commit Message Skill It is listed under Coding & Dev Tools on SkillMD.

Is Commit Messages safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Commit Messages?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Commit Messages free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Commit Messages?

ComeOnOliver (@comeonoliver) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Commit Messages by comeonoliver — Agent Skill

Name: Commit Messages
Author: ComeOnOliver

File contents

Commit Message Skill

Generate consistent, informative commit messages following the Conventional Commits specification.

When to Use This Skill

User asks to "commit", "write a commit message", or "prepare commit"
User has staged changes and mentions commits
Before any git commit command

Process

Analyze changes: Run git diff --staged to see what's being committed
Identify the type: Determine the primary change category
Find the scope: Identify the main area affected
Write the message: Follow the format below

Commit Message Format

<type>(<scope>): <description>

[optional body]

[optional footer(s)]

Types

Type	Description	Example
`feat`	New feature	`feat(auth): add OAuth2 login`
`fix`	Bug fix	`fix(api): handle null response`
`docs`	Documentation only	`docs(readme): add setup instructions`
`style`	Formatting, no code change	`style: fix indentation`
`refactor`	Code change, no new feature/fix	`refactor(db): extract query builder`
`perf`	Performance improvement	`perf(search): add result caching`
`test`	Adding/fixing tests	`test(auth): add login unit tests`
`build`	Build system changes	`build: update webpack config`
`ci`	CI configuration	`ci: add GitHub Actions workflow`
`chore`	Maintenance tasks	`chore(deps): update dependencies`
`revert`	Revert previous commit	`revert: feat(auth): add OAuth2`

Scope

The scope should be a noun describing the section of the codebase:

auth, api, db, ui, config
Feature names: search, checkout, dashboard
Or omit if change is broad

Subject Line Rules

Use imperative mood: "add" not "added" or "adds"
Don't capitalize first letter after colon
No period at the end
Max 72 characters total

Body (when needed)

Separate from subject with blank line
Explain what and why, not how
Wrap at 72 characters
Use bullet points for multiple changes

Footer (when needed)

BREAKING CHANGE: for breaking changes
Fixes #123 to close issues
Refs #456 to reference without closing

Examples

Simple feature

feat(search): add fuzzy matching support

Implement Levenshtein distance algorithm for typo tolerance
in search queries. Configurable via FUZZY_THRESHOLD env var.

Bug fix with issue reference

fix(cart): prevent duplicate items on rapid clicks

Add debounce to add-to-cart button and check for existing
items before insertion.

Fixes #234

Breaking change

feat(api)!: change response format to JSON:API

BREAKING CHANGE: API responses now follow JSON:API spec.
All clients need to update their parsers.

- Wrap data in `data` object
- Move metadata to `meta` object  
- Add `links` for pagination

Multiple related changes

refactor(auth): consolidate authentication logic

- Extract JWT handling to dedicated service
- Move session management from controller to middleware
- Add refresh token rotation

This prepares for the upcoming OAuth2 integration.

Output

When generating a commit message:

Show the staged changes summary
Propose the commit message
Explain the type/scope choice if non-obvious
Ask if the user wants to proceed or modify

---name: commit-messagesdescription: Commit Message Skill---# Commit Message SkillGenerate consistent, informative commit messages following the Conventional Commits specification.## When to Use This Skill- User asks to "commit", "write a commit message", or "prepare commit"- User has staged changes and mentions commits- Before any `git commit` command## Process1. **Analyze changes**: Run `git diff --staged` to see what's being committed2. **Identify the type**: Determine the primary change category3. **Find the scope**: Identify the main area affected4. **Write the message**: Follow the format below## Commit Message Format```<type>(<scope>): <description>[optional body][optional footer(s)]```### Types| Type | Description | Example ||------|-------------|---------|| `feat` | New feature | `feat(auth): add OAuth2 login` || `fix` | Bug fix | `fix(api): handle null response` || `docs` | Documentation only | `docs(readme): add setup instructions` || `style` | Formatting, no code change | `style: fix indentation` || `refactor` | Code change, no new feature/fix | `refactor(db): extract query builder` || `perf` | Performance improvement | `perf(search): add result caching` || `test` | Adding/fixing tests | `test(auth): add login unit tests` || `build` | Build system changes | `build: update webpack config` || `ci` | CI configuration | `ci: add GitHub Actions workflow` || `chore` | Maintenance tasks | `chore(deps): update dependencies` || `revert` | Revert previous commit | `revert: feat(auth): add OAuth2` |### ScopeThe scope should be a noun describing the section of the codebase:- `auth`, `api`, `db`, `ui`, `config`- Feature names: `search`, `checkout`, `dashboard`- Or omit if change is broad### Subject Line Rules- Use imperative mood: "add" not "added" or "adds"- Don't capitalize first letter after colon- No period at the end- Max 72 characters total### Body (when needed)- Separate from subject with blank line- Explain *what* and *why*, not *how*- Wrap at 72 characters- Use bullet points for multiple changes### Footer (when needed)- `BREAKING CHANGE:` for breaking changes- `Fixes #123` to close issues- `Refs #456` to reference without closing## Examples### Simple feature```feat(search): add fuzzy matching supportImplement Levenshtein distance algorithm for typo tolerancein search queries. Configurable via FUZZY_THRESHOLD env var.```### Bug fix with issue reference```fix(cart): prevent duplicate items on rapid clicksAdd debounce to add-to-cart button and check for existingitems before insertion.Fixes #234```### Breaking change```feat(api)!: change response format to JSON:APIBREAKING CHANGE: API responses now follow JSON:API spec.All clients need to update their parsers.- Wrap data in `data` object- Move metadata to `meta` object - Add `links` for pagination```### Multiple related changes```refactor(auth): consolidate authentication logic- Extract JWT handling to dedicated service- Move session management from controller to middleware- Add refresh token rotationThis prepares for the upcoming OAuth2 integration.```## OutputWhen generating a commit message:1. Show the staged changes summary2. Propose the commit message3. Explain the type/scope choice if non-obvious4. Ask if the user wants to proceed or modify

Frequently asked questions

Commit Messages