How do I install the Commit Message skill?

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

Generate concise Git commit messages in imperative mood. Use when the user asks to create, write, draft, make, generate, or suggest a commit message, or when they say "commit these changes", "what should I commit?", or ask for help with git commit. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

Git Commit Message Generator

Generate concise, descriptive Git commit messages in English.

Process

Run git diff --cached directly (NOT git -C <path> diff --cached, NOT cd <path> && git diff --cached) to check for staged changes
If staged changes exist: generate commit message based on staged changes only
If no staged changes: run git diff directly (NOT git -C <path> diff, NOT cd <path> && git diff) and git status directly (NOT git -C <path> status, NOT cd <path> && git status) to view unstaged and untracked files
For untracked files, intelligently assess which need content review (code/config files) vs which can be inferred from filename (assets, dependencies)
Generate a single-line commit message

Output

Output ONLY the commit message — a single line, no explanation, no follow-up questions, no code block fencing.

Format

Imperative mood, under 72 characters
Focus on the 'what' and 'why' of the change, not the 'how'. Avoid generic messages like 'update code' or 'fix bug'.
No type prefix (e.g., feat:, fix:) unless the user explicitly requests Conventional Commits format

Examples

Add user authentication with JWT tokens
Update navbar to include search functionality
Remove deprecated API endpoints
Rename userService to UserAccountService
Fix null pointer exception in user service
Improve error handling in payment module
Optimize database queries for faster loading
Refactor user service to use repository pattern
Document API endpoints in README
Add edge case tests for payment processing
Bump dependencies
Add login page with validation and error handling
Migrate CI pipeline from Travis to GitHub Actions
Fix authentication bug and update related tests

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

---name: commit-message-5description: Generate concise Git commit messages in imperative mood. Use when the user asks to create, write, draft, make, generate, or suggest a commit message, or when they say "commit these changes", "what should I commit?", or ask for help with git commit. Use when this capability is needed.---# Git Commit Message GeneratorGenerate concise, descriptive Git commit messages in English.## Process1. Run `git diff --cached` directly (NOT `git -C <path> diff --cached`, NOT `cd <path> && git diff --cached`) to check for staged changes2. If staged changes exist: generate commit message based on staged changes only3. If no staged changes: run `git diff` directly (NOT `git -C <path> diff`, NOT `cd <path> && git diff`) and `git status` directly (NOT `git -C <path> status`, NOT `cd <path> && git status`) to view unstaged and untracked files4. For untracked files, intelligently assess which need content review (code/config files) vs which can be inferred from filename (assets, dependencies)5. Generate a single-line commit message## OutputOutput ONLY the commit message — a single line, no explanation, no follow-up questions, no code block fencing.## Format- Imperative mood, under 72 characters- Focus on the 'what' and 'why' of the change, not the 'how'. Avoid generic messages like 'update code' or 'fix bug'.- No type prefix (e.g., `feat:`, `fix:`) unless the user explicitly requests Conventional Commits format## Examples```Add user authentication with JWT tokensUpdate navbar to include search functionalityRemove deprecated API endpointsRename userService to UserAccountServiceFix null pointer exception in user serviceImprove error handling in payment moduleOptimize database queries for faster loadingRefactor user service to use repository patternDocument API endpoints in READMEAdd edge case tests for payment processingBump dependenciesAdd login page with validation and error handlingMigrate CI pipeline from Travis to GitHub ActionsFix authentication bug and update related tests```---> Converted and distributed by [TomeVault](https://tomevault.io/claim/ycs77) — claim your Tome and manage your conversions.

Frequently asked questions