How do I install the Commit Message skill?

Run npx skillmds@latest add tomevault-io/commit-message-6 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.

Is Commit Message 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 Message?

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 Message free to use?

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

Who published Commit Message?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Commit Message by tomevault-io — Agent Skill

Name: Commit Message
Author: tomevault-io

Commit Message

Git commit message conventions with Semantic Versioning prefix. Use when creating commits, reviewing commit messages, or preparing releases. Ensures consistent commit format with type prefix (feat/fix/refactor/etc.) for automated changelog generation. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

Commit Message

Format

<type>(<scope>): <emoji> <subject>

<body>

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

Types (Semantic Versioning)

Type	Version Bump	Description
`feat`	MINOR	New feature for the user
`fix`	PATCH	Bug fix
`refactor`	PATCH	Code change (no feature/fix)
`perf`	PATCH	Performance improvement
`style`	-	Formatting, whitespace
`docs`	-	Documentation only
`test`	-	Adding/updating tests
`build`	-	Build system, dependencies
`ci`	-	CI configuration
`chore`	-	Maintenance tasks

Breaking Changes: Append ! after type → feat!: triggers MAJOR bump

Emoji Reference

Emoji	Usage
✨	New feature (feat)
🐛	Bug fix (fix)
♻️	Refactoring (refactor)
⚡	Performance (perf)
📝	Documentation (docs)
🔧	Configuration (chore)
⬆️	Dependency upgrade
🏹	Release

Examples

# Feature
feat(auth): ✨ add OAuth2 login support

# Bug fix
fix(api): 🐛 resolve null pointer in user service

# Refactoring
refactor(components): ♻️ unify BaseTag root element

# Release
chore(release): 🏹 4.0.6

# Breaking change
feat!(api): ✨ redesign authentication flow

BREAKING CHANGE: Auth tokens now use JWT format

Rules

Use imperative mood: "add feature" not "added feature"
Keep subject under 72 characters
Scope is optional but recommended for clarity
Body explains "why" not "what"
Reference issues: Fixes #123 or Closes #456
Always include Co-Authored-By for AI-assisted commits

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: commit-message-6description: Git commit message conventions with Semantic Versioning prefix. Use when creating commits, reviewing commit messages, or preparing releases. Ensures consistent commit format with type prefix (feat/fix/refactor/etc.) for automated changelog generation. Use when this capability is needed.---# Commit Message## Format```<type>(<scope>): <emoji> <subject><body>Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>```## Types (Semantic Versioning)| Type | Version Bump | Description ||------|--------------|-------------|| `feat` | MINOR | New feature for the user || `fix` | PATCH | Bug fix || `refactor` | PATCH | Code change (no feature/fix) || `perf` | PATCH | Performance improvement || `style` | - | Formatting, whitespace || `docs` | - | Documentation only || `test` | - | Adding/updating tests || `build` | - | Build system, dependencies || `ci` | - | CI configuration || `chore` | - | Maintenance tasks |**Breaking Changes**: Append `!` after type → `feat!:` triggers MAJOR bump## Emoji Reference| Emoji | Usage ||-------|-------|| ✨ | New feature (feat) || 🐛 | Bug fix (fix) || ♻️ | Refactoring (refactor) || ⚡ | Performance (perf) || 📝 | Documentation (docs) || 🔧 | Configuration (chore) || ⬆️ | Dependency upgrade || 🏹 | Release |## Examples```bash# Featurefeat(auth): ✨ add OAuth2 login support# Bug fixfix(api): 🐛 resolve null pointer in user service# Refactoringrefactor(components): ♻️ unify BaseTag root element# Releasechore(release): 🏹 4.0.6# Breaking changefeat!(api): ✨ redesign authentication flowBREAKING CHANGE: Auth tokens now use JWT format```## Rules1. Use imperative mood: "add feature" not "added feature"2. Keep subject under 72 characters3. Scope is optional but recommended for clarity4. Body explains "why" not "what"5. Reference issues: `Fixes #123` or `Closes #456`6. Always include Co-Authored-By for AI-assisted commits---> Converted and distributed by [TomeVault](https://tomevault.io/claim/annrie) — claim your Tome and manage your conversions.

Frequently asked questions

Commit Message

File contents

Commit Message

Format

Types (Semantic Versioning)

Emoji Reference

Examples

Rules

Related skills

Frequently asked questions

How do I install the Commit Message skill?

What does the Commit Message skill do?

Is Commit Message safe to use?

Which AI agents work with Commit Message?

Is Commit Message free to use?

Who published Commit Message?