How do I install the Commit Message skill?

Run npx skillmds@latest add ycs77/commit-message 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. 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?

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

Commit Message by ycs77 — Agent Skill

Name: Commit Message
Author: ycs77

Commit Message

Generates concise, intent-driven Git commit messages in imperative mood. Use when the user asks to create, write, draft, make, generate, or suggest a commit message, says "commit these changes" or "what should I commit?", or asks for help with a Git commit.

ycs77 99f343e 2.2 KB Updated Sep 17, 2026

File contents

Git Commit Message Generator

Generate concise, descriptive and intent-driven Git commit messages in English.

Process

Run git diff --cached directly 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 and git status directly 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)
Combine the diff with the intent supported by the conversation context; do not invent motivation that is not evident
Generate a single-line commit message that prioritizes known intent, then observable outcome, then the concrete change

Output

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

Format

In English, imperative mood, under 72 characters
Prefer the intended outcome over the edited file or implementation detail. If the intent is unknown, describe the concrete behavioral change.
No type prefix (e.g., feat:, fix:) unless the user explicitly requests Conventional Commits format

Examples

Add JWT authentication to protect account access
Add payment edge-case tests to prevent regressions
Validate login input before submitting credentials
Make search accessible from the navbar
Clarify installation requirements in README
Remove deprecated endpoints to simplify the API surface
Rename userService to clarify account responsibilities
Handle missing users during authentication
Fix database deadlock when updating concurrent balances
Preserve authentication behavior with regression tests
Return actionable errors when payment processing fails
Reduce page load time by batching database queries
Decouple user persistence with a repository pattern
Keep CI builds portable by migrating to GitHub Actions
Upgrade Vue to resolve hydration errors

---name: commit-messagedescription: Generates concise, intent-driven Git commit messages in imperative mood. Use when the user asks to create, write, draft, make, generate, or suggest a commit message, says "commit these changes" or "what should I commit?", or asks for help with a Git commit.---# Git Commit Message GeneratorGenerate concise, descriptive and intent-driven Git commit messages in English.## Process1. Run `git diff --cached` directly 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 and `git status` directly 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. Combine the diff with the intent supported by the conversation context; do not invent motivation that is not evident6. Generate a single-line commit message that prioritizes known intent, then observable outcome, then the concrete change## OutputOutput ONLY the commit message — a single line, no explanation, no code block fencing.## Format- In English, imperative mood, under 72 characters- Prefer the intended outcome over the edited file or implementation detail. If the intent is unknown, describe the concrete behavioral change.- No type prefix (e.g., `feat:`, `fix:`) unless the user explicitly requests Conventional Commits format## Examples```Add JWT authentication to protect account accessAdd payment edge-case tests to prevent regressionsValidate login input before submitting credentialsMake search accessible from the navbarClarify installation requirements in READMERemove deprecated endpoints to simplify the API surfaceRename userService to clarify account responsibilitiesHandle missing users during authenticationFix database deadlock when updating concurrent balancesPreserve authentication behavior with regression testsReturn actionable errors when payment processing failsReduce page load time by batching database queriesDecouple user persistence with a repository patternKeep CI builds portable by migrating to GitHub ActionsUpgrade Vue to resolve hydration errors```

Frequently asked questions