Git commit

Skill to4iki/skills/engineering/git-commit

A collection of agent skills.

Install

npx -y skills add to4iki/skills --skill git-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

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

Analyze changes, stage files, and commit with Conventional Commits. Use when the user asks to commit or run git commit.

SKILL.md

0.9 KB, 214 tokens by cl100k_base, as published. Nobody here has run it

Git Commit

Run only when the user asks to commit.

Procedure

Run in parallel: git status / git diff / git diff --staged
Stage individually with git add <files> (never git add .). Skip secrets (.env, credentials, tokens, etc.)
If unrelated changes are mixed, propose separate commits
Commit with Conventional Commits in English (Japanese only if the user explicitly asks). Focus the message on why:

git commit -m "$(cat <<'EOF'
<type>(<scope>): <subject>

<why if useful>
EOF
)"

Place EOF at the start of the line (no indentation). Include issue/task numbers in the body when available.

Verify with git status

Gotchas

If there is nothing to commit, stop and tell the user
If a hook (e.g. pre-commit) fails, stop and ask the user to fix it

Gives 2 of the 12 instructions most pr commit review skills give in 214 tokens

Counted across 888 of the 1,342 authors here whose files we hold, read 2026-08-06

use conventional commits formathere, and in 123 of 888, across 110 files
keep subject line under 72 charactersin 60 of 888, across 46 files
delete branches after mergein 50 of 888, across 37 files
use imperative mood in subject linein 50 of 888, across 41 files
use imperative mood in commit messagesin 45 of 888
generate a conventional commit messagein 42 of 888
make atomic commitsin 37 of 888, across 25 files
run tests before committingin 36 of 888, across 24 files
run project test suite to verify clean baselinein 35 of 888, across 7 files
run detected project setup commandsin 34 of 888, across 6 files
wrap commit body at 72 charactersin 32 of 888, across 25 files
split unrelated changes into separate commitshere, and in 32 of 888, across 27 files

Said here and by no other author read

skip secrets
start eof at column zero
include issue numbers in the commit body
verify the final status

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.