commit

What it does and when to use it

Use when the user asks to commit changes (make a git commit, write a commit message). Checks the diff and tests first.

How it works

SKILL.md has no level-two headings · 26 lines, 225 words

---
name: commit
description: Use when the user asks to commit changes (make a git commit, write a commit message). Checks the diff and tests first.
---
# Commit

Extra instructions: $ARGUMENTS

Current state:
- branch: !`git branch --show-current`
- status: !`git status --short`
- recent commits: !`git --no-pager log --oneline -n 5`

Steps:
1. Look at what will be committed: `git --no-pager diff HEAD --stat`, then the diff of files you did not
   change yourself in this session. Always pass `--no-pager`.
2. Do not commit: secrets (.env, keys, tokens), large binaries, build output, logs, personal data. If such
   files are in the status, leave them out and tell the user.
3. If the project has tests and code changed, run the relevant tests. If they fail, stop and report;
   do not commit broken code unless the user says so.
4. Stage explicit paths: `git add -- <file> <file>`. Use `git add -A` only if every changed file belongs
   in the commit.
5. Message: follow the style of the recent commits above (language, prefixes like `fix:`/`feat:`). First line
   up to 72 chars says what and why; add a short body only if the change is not obvious.
   On Windows pass a multi-line message with several `-m` flags: `git commit -m "title" -m "body"`.
6. Show the result: `git --no-pager log --oneline -n 1` and `git status --short`.

Never push, amend, rebase, reset or use --no-verify unless the user explicitly asked. If a hook fails,
fix the cause and make a new commit.

Versions

Database snapshot: 13.11.2026 · package version f75ee34228ce (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

• 100commit-message
  Write a git commit message for the current changes and optionally make the commit. Use when the user says "commit this", "write a commit message", "commit my changes", or asks to split work into commits.
• 100create-commit-message
  Generate a Conventional Commit message from staged git changes when the user asks to write a commit message, create a commit, or format a commit
• 100git-commit
  Use this skill when the user wants to make a Git commit or split changes into more than one commit. Also use it when the user types "/commit" or asks for a conventional commit. The skill examines the diff, stages the related files, writes a Conventional Commits message, and runs…
• 90commit-message
  Write a commit message for the staged changes that matches the repo's own style, and commit when asked. Use when asked to "write a commit message", "commit this", "commit my changes" or "what should this commit say".
• 100git-commit
  Use this skill when the user wants to make a Git commit or split changes into more than one commit. Also use it when the user types "/commit" or asks for a conventional commit. The skill examines the diff, stages the related files, writes a Conventional Commits message, and runs…
• 100git-commit
  Commit staged changes with conventional commit message. Use when user says "commit changes", "commit this", "save my changes", or wants to create a git commit.