How do I install the Commit Message skill?

Run npx skillmds@latest add nicanac/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?

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

Commit Message by nicanac — Agent Skill

Name: Commit Message
Author: nicanac

File contents

Commit Message Generator Skill

Generate conventional commit messages by analyzing repository changes following the Conventional Commits specification.

When to use this skill

Use this when you need to generate a commit message for staged or unstaged changes.
This is helpful for ensuring commit messages are standardized, descriptive, and follow best practices.
Triggered by user requests like:
- "Generate a commit message"
- "Create a commit for my changes"
- "What should my commit message be?"
- "Commit"

How to use it

Analyze Changes: Examine staged (git diff --cached) and unstaged (git diff) changes to understand the context.

Determine Commit Type: Select the appropriate type from the table below:

Type	Description
`feat`	New feature
`fix`	Bug fix
`docs`	Documentation only changes
`style`	Formatting, whitespace changes
`refactor`	Code restructuring without behavior change
`perf`	Performance improvement
`test`	Adding or correcting tests
`build`	Build system or dependency changes
`ci`	CI configuration changes
`chore`	Maintenance tasks
`revert`	Revert previous commit

Identify Scope: (Optional) Specify the affected codebase area (e.g., auth, api, ui).
Draft Message:
- Subject: Imperative mood, lowercase, no period (e.g., feat(auth): add login).
- Body: (Optional) Explain "what" and "why".
- Footer: (Optional) Breaking changes or issue references.

Output Format: Present the message in a code block, followed by the git command.

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

<optional body>

<optional footer>

Git Source:

git add . && git commit -m "<type>(<scope>): <description>" -m "<body>"

---name: commit-messagedescription: Generate conventional commit messages by analyzing repository changes following conventionalcommits.org specification---# Commit Message Generator SkillGenerate conventional commit messages by analyzing repository changes following the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) specification.## When to use this skill- Use this when you need to generate a commit message for staged or unstaged changes.- This is helpful for ensuring commit messages are standardized, descriptive, and follow best practices.- Triggered by user requests like: - "Generate a commit message" - "Create a commit for my changes" - "What should my commit message be?" - "Commit"## How to use it1. **Analyze Changes**: Examine staged (`git diff --cached`) and unstaged (`git diff`) changes to understand the context.2. **Determine Commit Type**: Select the appropriate type from the table below: | Type | Description | |------|-------------| | `feat` | New feature | | `fix` | Bug fix | | `docs` | Documentation only changes | | `style` | Formatting, whitespace changes | | `refactor` | Code restructuring without behavior change | | `perf` | Performance improvement | | `test` | Adding or correcting tests | | `build` | Build system or dependency changes | | `ci` | CI configuration changes | | `chore` | Maintenance tasks | | `revert` | Revert previous commit |3. **Identify Scope**: (Optional) Specify the affected codebase area (e.g., `auth`, `api`, `ui`).4. **Draft Message**: - Subject: Imperative mood, lowercase, no period (e.g., `feat(auth): add login`). - Body: (Optional) Explain "what" and "why". - Footer: (Optional) Breaking changes or issue references.5. **Output Format**: Present the message in a code block, followed by the git command. ``` <type>(<scope>): <short description> <optional body> <optional footer> ``` **Git Source:** ```bash git add . && git commit -m "<type>(<scope>): <description>" -m "<body>" ```

Frequently asked questions

Commit Message