How do I install the Mass Commit Message skill?

Run npx skillmds@latest add maiconsouza89/mass-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 Mass Commit Message safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: executes scripts, makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Mass 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 Mass Commit Message free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under CC-BY-4.

Who published Mass Commit Message?

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

Mass Commit Message by maiconsouza89

Name: Mass Commit Message
Rating: 4.2 (5 reviews)
Author: maiconsouza89

Mass Commit Message

Writes a Conventional Commits message from the staged diff, with a scope taken from the changed directories. Use when "write a commit message", "commit this" or "what scope should this commit have". Do NOT use for pull request descriptions (use mass-pr-description).

maiconsouza89 Updated Sep 22, 2026

File contents

Commit message

Produce one message in Conventional Commits 1.0.0 form: <type>(<scope>): <description>, an optional body, optional footers.

Steps

Read the staged diff: git diff --cached --stat and git diff --cached.
Run scripts/suggest-scope.sh to list the top-level directories touched by the staged changes. Use the single directory as the scope; with several, pick the one that carries the behaviour change, or omit the scope.
Pick the type from what the change does, not from where it lives: feat new behaviour · fix corrected behaviour · refactor same behaviour, new shape · docs · test · build dependencies and tooling · ci workflows · chore everything else.
Write the description in the imperative mood, lowercase, no trailing period, at most 72 characters including the prefix.
Add a body only when the diff does not explain itself: what was wrong, why this fix.
A breaking change gets ! after the scope and a BREAKING CHANGE: footer.

Output

Print the message inside a fenced block and nothing else. Do not run git commit unless the user asked for it in the same request.

Frequently asked questions