Skip to content
Back to skills

Commit 36

ASecurity

This skill should be used when the user asks to "commit changes", "create a commit", "git commit", or wants to save their staged changes with a meaningful message.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 27, 2026
code-qualitygit

Security analysis

A100/100

Scanned September 27, 2026

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

Installs into .claude/skills of the current project.

Are you the author of Commit 36?

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

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

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
description: This skill should be used when the user asks to "commit changes", "create a commit", "git commit", or wants to save their staged changes with a meaningful message.
---

# /commit

Create a git commit with a well-crafted message.

## Instructions

1. Run `git status` and `git diff --staged` to see changes
2. If nothing is staged, ask user what to stage or stage all with `git add -A`
3. Analyze the changes and create a commit message that:
   - Starts with a verb (Add, Fix, Update, Remove, Refactor)
   - Summarizes the "why" not just the "what"
   - Keeps first line under 72 characters
4. Commit with the message
5. Show the commit hash when done

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…