Skip to content
Back to skills

Commit

ASecurity

Git Commit Command

  • 2 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added February 10, 2026
toolsgitperformancedocumentation

Security analysis

A100/100

Scanned February 12, 2026

npx -y skills add sakuro/dotfiles --skill commit --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Commit?

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

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

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: Git Commit Command
---

# Commit

Create a git commit following project conventions.

## Workflow

1. Run project tests before committing (skip for documentation-only changes)
2. Stage specific files individually — never use `git add .` or `git add -A`
3. Review staged changes with `git diff --cached`
4. Commit using heredoc with single-quoted delimiter (`<<'EOF'`)

## Commit Message Rules

- Write in English, imperative mood ("Fix" not "Fixed")
- Start with `:emoji:` code (not raw Unicode), followed by a space
- No period at end of subject line
- Body: focus on WHAT and WHY, 2-3 bullet points max
- Omit changes that were written but not included in the final commit
- Never include AI attribution

## Emoji Codes

`:zap:` Performance · `:bug:` Bug fix · `:sparkles:` Feature · `:memo:` Documentation
`:recycle:` Refactor · `:art:` Structure/format · `:wrench:` Configuration
`:white_check_mark:` Tests · `:fire:` Remove · `:package:` Dependencies

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…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.