Commit

Skill sneg55/agent-starter/skills/commit

Create a single well-crafted git commit from current changes. Analyzes diff, follows repo's commit style, and writes a concise "why not what" message.From its SKILL.md

Install

npx -y skills add sneg55/agent-starter --skill commit

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

runs commandsInstructs the agent to run 5 commands, including `git status` and 4 more.

SKILL.md

2.0 KB, 408 tokens by cl100k_base, as published. Nobody here has run it

Git Commit

Context

Gather this context before committing:

Current git status: git status
Current git diff (staged and unstaged): git diff HEAD
Current branch: git branch --show-current
Recent commits: git log --oneline -10

Git Safety Protocol

NEVER update the git config
NEVER skip hooks (--no-verify, --no-gpg-sign, etc) unless the user explicitly requests it
CRITICAL: ALWAYS create NEW commits. NEVER use git commit --amend, unless the user explicitly requests it
Do not commit files that likely contain secrets (.env, credentials.json, etc). Warn the user if they specifically request to commit those files
If there are no changes to commit (i.e., no untracked files and no modifications), do not create an empty commit
Never use git commands with the -i flag (like git rebase -i or git add -i) since they require interactive input which is not supported

Task

Based on the changes, create a single git commit:

Analyze all staged changes and draft a commit message:
- Look at the recent commits to follow this repository's commit message style
- Summarize the nature of the changes (new feature, enhancement, bug fix, refactoring, test, docs, etc.)
- Ensure the message accurately reflects the changes and their purpose (i.e. "add" means a wholly new feature, "update" means an enhancement to an existing feature, "fix" means a bug fix, etc.)
- Draft a concise (1-2 sentences) commit message that focuses on the "why" rather than the "what"
Stage relevant files and create the commit using HEREDOC syntax:

git commit -m "$(cat <<'EOF'
Commit message here.
EOF
)"

Stage and create the commit in a single message. Do not do anything else.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most pr commit review skills give in 408 tokens

Counted across 1,055 of the 1,911 authors here whose files we hold, read 2026-09-06

Use conventional commit message formatin 150 of 1055, across 145 files
Announce skill usage at startin 78 of 1055
Use imperative mood for commit descriptionsin 54 of 1055, across 51 files
Add directory to gitignore if not ignoredin 52 of 1055, across 41 files
Use imperative mood for commit subjectin 52 of 1055
Run tests to verify clean baselinein 42 of 1055, across 32 files
Push branch to originin 40 of 1055, across 38 files
Verify worktree directory is ignored before creationin 39 of 1055, across 32 files
Delete branches after mergingin 38 of 1055, across 30 files
Create worktree with new branchin 37 of 1055, across 32 files
Wrap body text at 72 charactersin 36 of 1055, across 34 files
Auto-detect and run project setupin 35 of 1055, across 27 files

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.