commit

Q: How do I install commit?

Run npx skills add https://github.com/helderberto/agent-skills --skill commit in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/commit/ (personal) or .claude/skills/commit/ (project).

by helderbertoCode Quality & Workflow

Group unstaged changes into atomic commits by concern, matching repository style. Use when asked to "commit", "create a commit", or "commit changes". Don't use for pushing or pull requests (/to-pr).

Installs: 59
Last 24h: —
Trending rank: —
Security: Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/helderberto/agent-skills --skill commit

01
Install
Run the command in your project. The CLI asks which agents to install for.
02
Describe the task
Ask your agent for something this skill covers. It loads commit automatically when relevant.
03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

Git Commit

Group all unstaged/untracked changes into atomic commits — one commit per logical concern. A single concern is just the degenerate case: one commit. Never push — pushing belongs to /hb:to-pr.

Paths in $ARGUMENTS scope the run: commit only those files and leave the rest of the tree as it is.

Message style

Match the repo's existing commit patterns from git log. Extreme concision — sacrifice grammar for brevity. Focus on "why" not "what". Imperative mood. Conventional commits (feat/fix/refactor/docs/chore + scope) when the repo uses them.

Workflow

Review full diff and status; read recent log for style.
Identify logical groups: feature/fix, its tests, config, formatting-only, docs, assets.
Per group: stage those files explicitly by name, commit with a HEREDOC message, confirm git status before the next group.
Finish with a clean working tree (scoped run: every listed file committed). Unsure how to group a file → ask.

Grouping rules

Formatting-only changes (whitespace, quotes, indentation) get their own commit, separate from logic.
A file with both logic and formatting changes stays in the logic commit.
Tests and the code they test can share a commit.
Pre-commit hook fails → fix, re-stage, create a new commit; never --amend, never skip hooks.

FAQ

What does the commit skill do?

Group unstaged changes into atomic commits by concern, matching repository style. Use when asked to "commit", "create a commit", or "commit changes". Don't use for pushing or pull requests (/to-pr).

How do I install commit?

Run npx skills add https://github.com/helderberto/agent-skills --skill commit in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/commit/ (personal) or .claude/skills/commit/ (project).

Which AI agents can use commit?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is commit safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains commit?

It is published by helderberto in helderberto/agent-skills. It has 59 recorded installs.

More from helderberto/agent-skills

View all →

code-review

helderberto/agent-skills

Correctness lens for a PR or diff, used by build and review — bugs, security, performance, and code quality. Use when asked to review a PR or give pull request feedback, even when the diff is pasted inline. Don't use for local uncommitted changes, creating PRs, or merging.

Code Quality & Workflow623 installs