How do I install the Commit Msg skill?

Run npx skillmds@latest add tomevault-io/commit-msg-2 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 Msg 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 Msg?

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

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

Who published Commit Msg?

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

Commit Msg by tomevault-io — Agent Skill

Name: Commit Msg
Author: tomevault-io

Commit Msg

Analyze git commits and generate better commit messages based on actual changes. Use when amending commit messages, reviewing commit quality, or writing commits. Triggers on terms like "commit message", "amend commit", "fix commits", "reword commits". Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

Commit Message Skill

Generates and improves commit messages following conventional commits format.

Conventional Commits Format

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

[optional body]

[optional footer]

Types

Type	Use For
`feat`	New feature
`fix`	Bug fix
`docs`	Documentation only
`style`	Formatting, no code change
`refactor`	Code change that neither fixes a bug nor adds feature
`perf`	Performance improvement
`test`	Adding or updating tests
`chore`	Maintenance tasks
`ci`	CI/CD changes
`build`	Build system changes

Scopes for This Project

Scope	Description
bits	BitVec, rank/select, popcount
bp	Balanced parentheses
json	JSON semi-indexing
jq	jq query language
simd	SIMD implementations
cli	CLI tool
bench	Benchmarks
docs	Documentation

Examples

Feature Addition

feat(json): add PFSM table-driven parser

Implements parallel finite state machine approach from hw-json-simd.
Achieves 880 MiB/s throughput on x86_64 (AMD Zen 4), 40-77% faster than scalar.

Bug Fix

fix(bp): correct find_close for edge case at word boundary

Fixes #42

Performance Improvement

perf(popcount): add AVX-512 VPOPCNTDQ implementation

5.2x faster than scalar for large bitvectors.
Requires Intel Ice Lake+ or AMD Zen 4+.

Refactoring

refactor(jq): replace deprecated last() with next_back()

Removes dead code and simplifies iterator handling.

Instructions

Read the staged changes with git diff --cached
Understand what changed and why
Choose appropriate type and scope
Write a concise subject line (50 chars ideal, 72 max)
Add body if changes need explanation
Include footer for breaking changes or issue references

Commit Message Rules

Subject line: Imperative mood ("add" not "added")
No period at end of subject line
Blank line between subject and body
Body: Explain what and why, not how
Footer: Reference issues, note breaking changes

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

---name: commit-msg-2description: Analyze git commits and generate better commit messages based on actual changes. Use when amending commit messages, reviewing commit quality, or writing commits. Triggers on terms like "commit message", "amend commit", "fix commits", "reword commits". Use when this capability is needed.---# Commit Message SkillGenerates and improves commit messages following conventional commits format.## Conventional Commits Format```<type>(<scope>): <description>[optional body][optional footer]```## Types| Type | Use For ||------------|-------------------------------------------------------|| `feat` | New feature || `fix` | Bug fix || `docs` | Documentation only || `style` | Formatting, no code change || `refactor` | Code change that neither fixes a bug nor adds feature || `perf` | Performance improvement || `test` | Adding or updating tests || `chore` | Maintenance tasks || `ci` | CI/CD changes || `build` | Build system changes |## Scopes for This Project| Scope | Description ||--------|--------------------------------------|| bits | BitVec, rank/select, popcount || bp | Balanced parentheses || json | JSON semi-indexing || jq | jq query language || simd | SIMD implementations || cli | CLI tool || bench | Benchmarks || docs | Documentation |## Examples### Feature Addition```feat(json): add PFSM table-driven parserImplements parallel finite state machine approach from hw-json-simd.Achieves 880 MiB/s throughput on x86_64 (AMD Zen 4), 40-77% faster than scalar.```### Bug Fix```fix(bp): correct find_close for edge case at word boundaryFixes #42```### Performance Improvement```perf(popcount): add AVX-512 VPOPCNTDQ implementation5.2x faster than scalar for large bitvectors.Requires Intel Ice Lake+ or AMD Zen 4+.```### Refactoring```refactor(jq): replace deprecated last() with next_back()Removes dead code and simplifies iterator handling.```## Instructions1. Read the staged changes with `git diff --cached`2. Understand what changed and why3. Choose appropriate type and scope4. Write a concise subject line (50 chars ideal, 72 max)5. Add body if changes need explanation6. Include footer for breaking changes or issue references## Commit Message Rules1. **Subject line**: Imperative mood ("add" not "added")2. **No period** at end of subject line3. **Blank line** between subject and body4. **Body**: Explain what and why, not how5. **Footer**: Reference issues, note breaking changes---> Converted and distributed by [TomeVault](https://tomevault.io/claim/rust-works) — claim your Tome and manage your conversions.

Frequently asked questions