
Contextual Commits
Writes git commit messages that record the why behind code changes, not just the what.
- Repository
- yamadashy/repomix
- Stars
- 29,118
- Licence
- MIT
- Files
- 1 file
What it does
When the agent commits code, it adds structured lines to the commit body that record the user's intent, the decisions made, alternatives rejected, constraints discovered, and things learned. Standard Conventional Commit subject lines are kept as they are. This preserves reasoning that a diff alone cannot show, so future developers or agent sessions can understand why the code was written.
Great for
- Developers who want richer git history explaining motivation and trade-offs
- Teams using AI agents for commits who want decisions recorded for later sessions
- Projects that already follow Conventional Commits and want to extend them
Skip it if
- Trivial changes such as typo or alignment fixes, where the skill itself says extra lines are noise
- Teams with strict commit message formats that reject extra body lines, since the skill adds action lines to every non-trivial commit
- Situations where the agent lacks context: the skill warns it should only write what the diff evidences for changes it did not make, so reasoning may be inferred or thin
Try asking
- “Commit my staged changes for the new OAuth login flow”
- “Finish this task and commit it with context on the decisions we made”
- “Commit these changes and record why we rejected the other library”
Install in 3 steps
- 1
Download the skill
The ZIP contains the 1 original files, the MIT licence and an attribution note.
contextual-commit.zip - 2
Add it to your agent
Claude Code (all projects)
mkdir -p ~/.claude/skills && unzip contextual-commit.zip -d ~/.claude/skills/Claude Code / Agent SDK (this project only)
mkdir -p .claude/skills && unzip contextual-commit.zip -d .claude/skills/Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.
- 3
Ask for the task
No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.
Get better results
- Stage the exact files you want before asking the agent to commit, since staged changes define the commit scope.
- Explain the reasoning and rejected alternatives during the session so the agent can record them accurately.
- Review the generated commit body, since the agent may infer reasoning for changes it did not produce.
What's inside
- SKILL.md
Redistributed unmodified from yamadashy/repomix under the MIT licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.