
commit
Stage and commit changes to git following conventional commits format. Use when asked to commit, create a commit, or save changes. Drafts meaningful commit messages by understanding the why, not just the what. Never amends published commits, never skips hooks, never uses git add -A. Stages specific files by name. Does not push — that is the gh skill's job.
- Installs
- 41
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/paulnsorensen/skillz-that-grillz --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.
commit
Stage and commit. Conventional commits. No push.
Protocol
Run in parallel first:
git status
git diff HEAD
git log --oneline -5
Then sequentially:
- Understand the why — read the diff, understand what changed and why
- Stage specific files — by name, never
git add -Aorgit add . - Draft the message — see format below
- Commit via heredoc (preserves formatting)
- Verify with
git status
Commit message format
type(scope): short description (≤72 chars)
Optional body if nuance is lost without it.
Co-Authored-By: <agent-name> <agent-email>
The Co-Authored-By trailer is optional — fill in the agent identity your
harness provides, or omit the line entirely if the project doesn't want it.
Types: feat, fix, refactor, chore, docs, test, style
Focus on the why, not the what. The diff already shows what changed.
Use a heredoc to preserve formatting:
git commit -m "$(cat <<'EOF'
type(scope): short description
Co-Authored-By: <agent-name> <agent-email>
EOF
)"
Rules
- Never amend unless explicitly asked — create new commits instead
- Never --no-verify — don't skip hooks
- Never force-push to main/master
- No push, no PR — hand off to the gh skill for that
- Hook fails? Fix the issue, re-stage, create a new commit (not amend)
- Don't commit
.env, credentials, or large binaries — warn the user
Gotchas
- Heredoc commit messages with backticks or
$need single-quoted delimiter (<<'EOF'not<<EOF) - If prek hook fails, the commit did NOT happen — create a new commit after fixing, never amend
- Co-Authored-By trailer is optional — use the agent identity your harness exposes, or drop the line if the project doesn't track agent authorship
- Empty
git diff HEADafter staging means nothing new was added — checkgit diff --cachedinstead
FAQ
What does the commit skill do?
Stage and commit changes to git following conventional commits format. Use when asked to commit, create a commit, or save changes. Drafts meaningful commit messages by understanding the why, not just the what. Never amends published commits, never skips hooks, never uses git add -A. Stages specific files by name. Does not push — that is the gh skill's job.
How do I install commit?
Run npx skills add https://github.com/paulnsorensen/skillz-that-grillz --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 paulnsorensen in paulnsorensen/skillz-that-grillz. It has 41 recorded installs.
More from paulnsorensen/skillz-that-grillz
skillz
paulnsorensen/skillz-that-grillz
Add, improve, audit, wedge, or autoimprove a skill. Improve and audit also accept a sub-agent definition. The result runs predictably on Claude Code, Codex, OMP, and other Agent Skills hosts. Use for /skillz , "improve this skill", "autoimprove this skill", "optimize this skill", "tighten this skill", "audit this agent", "new skill for X", "skill not triggering", "fix trigger rate", "wedge this", "turn this repeated work into a CLI", or "what in this skill should be a CLI". Do NOT use for CLAUDE.md or system-prompt edits, or for code changes that a cheese pipeline skill owns.
gh
paulnsorensen/skillz-that-grillz
Complete GitHub tasks using the gh CLI — pull request inspection, review, and merge, issues, CI checks, releases, workflow runs, code search, repo and label management. Use when the user says "merge PR", "check CI", "list issues", "review PR", "PR status", "close issue", "trigger workflow", "view release", "search repos", or invokes /gh. Use git (log, diff, status) for read-only local context only. Do NOT use for committing, staging, pushing, or PR creation — use /plate for those. Do NOT use for code-quality review — use a dedicated review skill.
chezmoi
paulnsorensen/skillz-that-grillz
Manage dotfiles with chezmoi — the source-state dotfile manager that uses filename attributes (dot, private, encrypted, runonce), Go templates, and password-manager integration to keep one set of dotfiles working across many machines. Use when the user says "set up dotfiles", "manage my dotfiles", "bootstrap a new machine", "chezmoi", "encrypt my SSH key in dotfiles", "template dotfiles per OS", "add secrets to dotfiles", "what should be in my .chezmoi.toml.tmpl", or asks how to share configs across macOS / Linux / servers. Also trigger when the user is staring at a fresh machine and wants the one-liner that gets them home, or when they're about to commit something sensitive into a dotfiles repo. Do NOT use for stow / yadm / rcm or other dotfile managers, generic git repo setup, or password-manager setup unrelated to dotfiles.
prek
paulnsorensen/skillz-that-grillz
Onboard prek (Rust-powered pre-commit) into any project and suggest hooks tailored to the language/framework. Use when the user says "add prek", "set up pre-commit hooks", "configure prek", "what hooks should I use", or when you notice a project without a prek.toml that would benefit from pre-commit checks. Also trigger when the user wants to add new hooks to an existing prek.toml, audit their hook config, or migrate from pre-commit to prek. Covers Rust, Python, TypeScript/JavaScript, Go, Ruby, and Shell projects. Do NOT use for husky, lint-staged, or CI pipeline hook configuration — this skill is specifically for prek.
github-copilot-personal-instructions
paulnsorensen/skillz-that-grillz
Add or audit GitHub Copilot personal custom instructions — the per-user prompt configured at github.com/copilot that applies to every Copilot Chat conversation that account has on github.com. Covers where to set them, what they do and don't apply to (github.com Chat only — not IDE, not mobile, not coding agent), how they merge with repository and organization instructions, and verification. Use when the user says "set personal Copilot instructions", "configure my Copilot", "Copilot keeps responding in the wrong language", "make Copilot use my preferred tone", "personal Copilot prompt", "user-level Copilot config", "Copilot is ignoring my preferences", or invokes /github-copilot-personal-instructions. Do NOT use for repository-scoped instructions — that is /github-copilot-repo-instructions.
Popular code quality & workflow skills
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
improve-codebase-architecture
mattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
handoff
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
domain-modeling
mattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
codebase-design
mattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.