Committing Code
Groups pending git changes into logical Conventional Commits, with a secrets guard and an approval pause before each commit.
Test report
- Verdict
- Tested · Works
- Score
- Tested
- Jul 15, 2026
- Environment
- Claude Code 2.x (agent harness)
- Upstream re-checked
- Aug 10, 2026 · 34f76b5
Ran it for real on a throwaway repo with three unrelated pending changes (a bug fix, a new test file, a new README): the skill's own read-only gather script correctly flagged the mixed-purpose diff, and it produced three clean Conventional Commits (fix/test/docs) versus a naive baseline of one lumped, unconventionally-worded commit.
Scored on four weighted criteria — install, triggering, output vs. baseline, docs. How scoring works
- Installs cleanly 5/5
- Triggers reliably 5/5
- Output vs. baseline 8/10
- Docs & honesty 4/5
What Committing Code does
Inspects git status/diff/log and proposes one commit for small coherent changesets or multiple purpose-grouped commits (feat/fix/docs/test/etc.) for mixed changesets, refusing to stage likely secrets and pausing for user approval before running git add/commit. Triggers on committing, saving changes, creating commits, or grouping work into commits; explicitly excludes amend/rebase/force-push/history-rewrite requests.
How to install Committing Code
git clone https://github.com/alexei-led/cc-thingz
cd cc-thingz
mkdir -p ~/.claude/skills
cp -r src/skills/committing-code ~/.claude/skills/committing-code
Skills live in ~/.claude/skills/ (global) or .claude/skills/
(per-project). Restart Claude Code after installing.
Commands — how to trigger Committing Code
-
/committing-codeGroups pending git changes into logical Conventional Commits, with a secrets guard and an approval pause before each commit.
It also activates on plain-language prompts like these:
-
I've got three unrelated changes staged, group them into clean commits -
Save my changes as Conventional Commits, splitting fix from docs and tests -
Check my diff for secrets before committing this batch of changes
Frequently asked questions
- Is the Committing Code skill free?
- Yes. The skill itself is free from alexei-led/cc-thingz. SkillProof publishes the install command and an independent test verdict at no cost.
- Does Committing Code work with Claude Code?
- We tested it with Claude Code 2.x (agent harness) on Jul 15, 2026. Verdict: Tested · Works. Ran it for real on a throwaway repo with three unrelated pending changes (a bug fix, a new test file, a new README): the skill's own read-only gather script correctly flagged the mixed-purpose diff, and it produced three clean Conventional Commits (fix/test/docs) versus a naive baseline of one lumped, unconventionally-worded commit.
- What is the Committing Code SkillProof Score?
- 8.8/10 — installs cleanly 5/5, triggers reliably 5/5, output vs. baseline 8/10, docs & honesty 4/5.
- How do I install Committing Code?
- Copy the install command from this page, run it in your terminal, and restart Claude Code. Skills live in ~/.claude/skills/ (global) or .claude/skills/ inside a project.
- Can I use Committing Code with Cursor, Copilot, Gemini CLI, Codex or other AI tools?
- The SKILL.md format is native to Claude (Claude Code, Desktop, claude.ai). The instructions inside adapt to other assistants: Cursor rules, GitHub Copilot instructions, Windsurf rules, Custom GPTs, AGENTS.md for OpenAI Codex, and GEMINI.md for Google Gemini CLI — our conversion guides cover each, and the free converter on the tools page does the wrapping for you.