Git commit
Analyze changes, stage files, and commit with Conventional Commits. Use when the user asks to commit or run git commit.From its SKILL.md
npx -y skills add to4iki/skills --skill git-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.
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>(nevergit 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
What ships with it: 1 file
1.2 KB alongside SKILL.md
- SKILL-ja.md1.2 KB