Skip to content
Back to skills

Committing

ASecurity

Guidelines for git commit messages

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 27, 2026
documentationgit

Security analysis

A100/100

Scanned September 27, 2026

npx -y skills add David-Li0406/meta-skill-evloving --skill committing --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Committing?

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

Security grade badge for Committing
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/david-li0406-committing/badge)](https://www.skillsdirectory.com/skills/david-li0406-committing)

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: committing
description: Guidelines for git commit messages
---

Commit only when user requests or as part of an explicit defined task.

- Use prefix: `fix:`, `feat:`, `docs:`, `wip:`, etc.
- Explain WHY from end user perspective, not WHAT changed
- Be specific — avoid generic messages like "improved agent experience"
- Keep brief — used for release notes

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…