Skip to content
Back to skills

Commit Message Generator

ASecurity

Generate appropriate commit messages based on Git diffs

  • 416 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added February 7, 2026
ai-agentsrefactoringgit

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned February 12, 2026

npx -y skills add aiskillstore/marketplace --skill commit-message-generator --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Commit Message Generator?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Commit Message Generator
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aiskillstore-commit-message-generator/badge)](https://www.skillsdirectory.com/skills/aiskillstore-commit-message-generator)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: commit-message-generator
description: Generate appropriate commit messages based on Git diffs
---

## Prerequisites
- This Skill retrieves Git diffs and suggests meaningful commit messages
- Message format should follow Conventional Commits
- Commit messages should have a one-line Conventional Commits header, an optional blank second line, and from the third line onward include a bulleted list summarizing the changes
- Commit messages should be in English
- **Never perform Git commit or Git push**

## Steps
1. Run `git status` to check modified files
2. Retrieve diffs with `git diff` or `git diff --cached`
3. Analyze the diff content and determine if changes should be split into multiple commits
4. For each logical group of changes:
   - List the target files
   - Generate a message in English compliant with Conventional Commits
   - Suggest the command: `git add <files> && git commit -m "<message>"`
5. If changes are extensive and should be split, provide:
   - Rationale for the split
   - Multiple commit suggestions with their respective target files and messages

## Commit Splitting Guidelines
- Split commits when changes span multiple logical concerns (e.g., feature + refactoring)
- Group related files that serve the same purpose
- Keep each commit focused on a single, atomic change

## Notes
- **This Skill must never execute `git commit` or `git push`**
- Only suggest commands; execution is entirely at user's discretion
- Users must explicitly perform commits and pushes themselves

Files in this skill

  • SKILL.md1.5 KB
  • skill-report.json9.1 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…