Git Commits
- 501 installs
- 3.9k repo stars
- Updated January 26, 2026
- parcadei/continuous-claude-v3
git-commits is a Claude Code routing skill that forces the `/commit` workflow instead of raw `git commit` for developers who need clean, user-authored commit messages without Claude Code co-author attribution lines.
About
git-commits is a ship-phase Git skill from Continuous-Claude-v3 that intercepts commit, push, and save-to-git requests in Claude Code. Instead of running `git commit` directly—which adds "Generated with Claude Code" and Co-Author trailers—it mandates `Skill("commit")` so commits appear user-authored. The `/commit` skill also generates `reasoning.md` capturing what was attempted, clears build-attempt state for the next feature, and optionally runs `generate-reasoning.sh` with the commit hash before `git push origin <branch>`. Trigger words include commit, push, save changes, and push to GitHub. The skill is user-invocable false—it activates automatically when agents would otherwise commit. Developers using Continuous-Claude-v3 reach for it implicitly whenever they want disciplined commit hygiene integrated with session reasoning capture.
- Automatically generates conventional commit messages from staged changes
- Analyzes diff context to produce accurate, descriptive titles and bodies
- Enforces conventional commit standards for better changelog generation
- Works directly with Claude, Cursor and other agents via MCP
- Reduces context switching between editor and terminal
Git Commits by the numbers
- 501 all-time installs (skills.sh)
- +2 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #107 of 733 Git & Pull Requests skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/parcadei/continuous-claude-v3 --skill git-commitsAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 501 |
|---|---|
| repo stars | ★ 3.9k |
| Last updated | January 26, 2026 |
| Repository | parcadei/continuous-claude-v3 ↗ |
How do you commit without Claude co-author lines?
Let their coding agent create clear, conventional git commits without leaving the flow.
Who is it for?
Claude Code users on Continuous-Claude-v3 who want standardized commits with reasoning capture and no Generated-with-Claude trailers.
Skip if: Repositories or agents that intentionally keep AI co-author attribution or use plain `git commit` without Continuous-Claude workflows.
When should I use this skill?
User says commit, push, save changes, push to github, or commit and push during a Continuous-Claude-v3 session.
What you get
Clean git commit without AI attribution, reasoning.md session capture, and optional pushed branch on origin.
- Clean git commit
- reasoning.md
- Pushed branch optional
By the numbers
- Mandates 1 dedicated /commit skill invocation instead of direct git commit
- Generates reasoning.md plus optional generate-reasoning.sh post-commit step
- Lists 5+ trigger phrases including commit, push, and save changes
Files
Git Commit Rules
When the user asks to commit, push, or save changes to git:
MUST Use /commit Skill
DO NOT run git commit directly. Instead:
Skill("commit")The /commit skill: 1. Removes Claude attribution from commits 2. Generates reasoning.md capturing what was tried 3. Clears build attempts for next feature
Why This Matters
- Regular
git commitadds "Generated with Claude Code" and Co-Author lines - The
/commitskill removes these so commits appear user-authored - Reasoning capture preserves build history for future sessions
Trigger Words
When you see these in user prompts, use the commit skill:
- "commit", "push", "save changes"
- "push to github", "push changes"
- "commit and push"
After Commit
The skill will prompt you to run:
bash "$CLAUDE_PROJECT_DIR/.claude/scripts/generate-reasoning.sh" <hash> "<message>"Then push if requested:
git push origin <branch>Related skills
Caveman CommitGenerate terse, Conventional Commits messages that preserve intent without fluff or AI attribution.272k94k
Resolving Merge ConflictsQuickly understand, resolve, and commit merge conflicts without losing work or breaking their flow.183k193kGit Guardrails Claude CodePrevent Claude Code from accidentally running destructive git commands like force push, hard reset, or clean.175k193k
Using Git WorktreesGuarantee every new feature or implementation task runs inside a clean, isolated workspace without polluting the main branch or current working directory.149k263k
Git CommitGenerate accurate conventional commit messages and intelligently stage files directly from natural language requests.40.6k37.2k
Resolve Merge ConflictsQuickly understand and resolve Git merge conflicts without losing context or breaking changes.16.5k148FAQ
Why does git-commits block direct git commit?
git-commits blocks raw `git commit` because Claude Code adds "Generated with Claude Code" and Co-Author trailers. The `/commit` skill removes those lines so history appears user-authored.
What does git-commits create besides the commit?
git-commits triggers `/commit`, which writes reasoning.md capturing attempted approaches, clears build-attempt state, and may run generate-reasoning.sh with the new commit hash before pushing.
Which phrases activate git-commits?
git-commits activates on user prompts containing commit, push, save changes, push to github, or commit and push—routing the agent to Skill("commit") automatically.