How do I install the Commit Message skill?

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

Use when the user wants to write a git commit message — including 'write a commit message', 'commit this', or when they paste a diff / staged changes and ask what to commit it as. Follows Conventional Commits. Do NOT use for PR descriptions (use pr-description skill).

tomevault-io Updated Sep 17, 2026

File contents

Commit Message Writer

Write commit messages that follow Conventional Commits.

Format

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

<body>

<footer>

type (required): one of feat, fix, refactor, test, chore, docs
scope (optional): the module/area touched, e.g. auth, api, parser
subject (required): imperative mood, lowercase, no period, ≤ 50 chars
body (optional): wrap at 72 chars, explain why not what
footer (optional): BREAKING CHANGE: ... or Closes #123

Rules

Subject line in imperative mood: "add login form", not "added" or "adds".
Blank line between subject and body, and between body and footer.
Use ! after type/scope for breaking changes: feat(api)!: drop v1 endpoints.
One commit = one logical change. If the diff covers multiple concerns, suggest splitting.
Never put file names in the subject. Use scope instead.

Workflow

Ask for the diff or git status output if not provided.
Determine type from the nature of the change (new feature → feat, bugfix → fix, etc.).
Pick a scope from the most-touched directory or module.
Write subject, then body only if context is non-obvious.
Add BREAKING CHANGE: footer if applicable.

Examples

feat(auth): add OAuth login via GitHub

Users can now sign in with their GitHub account. Uses the standard
OAuth2 flow; tokens are stored in httpOnly cookies.

Closes #142

fix(parser): handle empty input without crashing

refactor(api)!: rename /users endpoint to /accounts

BREAKING CHANGE: /users is removed. Update clients to use /accounts.

Source: sunnykgupta/AI-Helpers — distributed by TomeVault.

---name: commit-message-7description: Use when the user wants to write a git commit message — including 'write a commit message', 'commit this', or when they paste a diff / staged changes and ask what to commit it as. Follows Conventional Commits. Do NOT use for PR descriptions (use pr-description skill).---# Commit Message WriterWrite commit messages that follow [Conventional Commits](https://www.conventionalcommits.org/).## Format```<type>(<scope>): <subject><body><footer>```- **type** (required): one of `feat`, `fix`, `refactor`, `test`, `chore`, `docs`- **scope** (optional): the module/area touched, e.g. `auth`, `api`, `parser`- **subject** (required): imperative mood, lowercase, no period, ≤ 50 chars- **body** (optional): wrap at 72 chars, explain *why* not *what*- **footer** (optional): `BREAKING CHANGE: ...` or `Closes #123`## Rules- Subject line in imperative mood: "add login form", not "added" or "adds".- Blank line between subject and body, and between body and footer.- Use `!` after type/scope for breaking changes: `feat(api)!: drop v1 endpoints`.- One commit = one logical change. If the diff covers multiple concerns, suggest splitting.- Never put file names in the subject. Use scope instead.## Workflow1. Ask for the diff or `git status` output if not provided.2. Determine type from the nature of the change (new feature → `feat`, bugfix → `fix`, etc.).3. Pick a scope from the most-touched directory or module.4. Write subject, then body only if context is non-obvious.5. Add `BREAKING CHANGE:` footer if applicable.## Examples```feat(auth): add OAuth login via GitHubUsers can now sign in with their GitHub account. Uses the standardOAuth2 flow; tokens are stored in httpOnly cookies.Closes #142``````fix(parser): handle empty input without crashing``````refactor(api)!: rename /users endpoint to /accountsBREAKING CHANGE: /users is removed. Update clients to use /accounts.```---> Source: [sunnykgupta/AI-Helpers](https://github.com/sunnykgupta/AI-Helpers) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions