Commit
Skill Stoica-Mihai/claude-skills/plugins/commit/skills/commit
Curated Claude Code plugin marketplace — OpenSpec extensions and autonomous development workflows
npx -y skills add Stoica-Mihai/claude-skills --skill commitAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Handles git commits with concise, list-style messages and no co-author trailers. Use this skill whenever the user asks to commit, says "commit", "/commit", "commit this", "save my changes", or any variation of requesting a git commit. This skill MUST be used for every commit operation — it overrides the default commit behavior.
SKILL.md
2.3 KB, as published. Nobody here has run it
Commit
Create clean, minimal git commits. No fluff, no co-author lines.
Process
- Run
git statusandgit diff(staged + unstaged) to understand what changed. Also rungit log --oneline -5to match the repo's existing message style. - Read the full output. Never truncate diffs or logs with
head,tail, line limits, or any other form of partial reading. A truncated diff means you're guessing about changes you haven't seen — and that leads to wrong or vague commit messages. If the diff is large, read all of it before writing the message. The quality of the commit message depends entirely on seeing the complete picture. - Stage the relevant files by name — avoid
git add -Aorgit add .to prevent accidentally staging secrets or junk. - Write a commit message following the format below.
- Commit. Do not push unless explicitly asked.
Message format
Use a single-line summary in conventional commit style (fix:, feat:, refactor:, docs:, chore:, test:), lowercase, no period. Keep it under 72 characters.
If multiple distinct changes are staged, use a bulleted list body:
feat: add volume slider and notification history
- wire up PipeWire volume control with mute toggle
- add notification history dropdown in bar capsule
The summary line should capture the overall theme; bullets cover the specifics. Skip the body if one line says it all.
Rules
- No Co-Authored-By trailers. Ever.
- No trailing summaries. Don't narrate what you just committed — the user can read the diff.
- Don't commit files that look like secrets (
.env, credentials, tokens). Warn if the user asks to. - Use a HEREDOC to pass the message so multi-line formatting is preserved:
git commit -m "$(cat <<'EOF' feat: the summary line - detail one - detail two EOF )" - If there are no changes to commit, say so and stop.
- If a pre-commit hook fails, fix the issue and create a new commit — never amend.