Who it is forA developer after a long agent session with dozens of unrelated file changes.
The problemOne giant commit makes history useless and review hard.
The outcomeSeveral logical Conventional Commits instead of one blob.
What you need first
- An agent that supports Agent Skills
- Node.js for the Skills CLI install
Steps
- Install with
npx skills add musoyangrigor/gitx-skill --skill gitx - Start a new agent session
- Run
$gitxto inspect changes and create a smart commit - Use
$gitx bodywhen you want commit bodies
Prompt for your agent
Use $gitx in <repo> to split the current changes into Conventional Commits. List the commits created and confirm no secrets were staged.
Caveat. A bare $gitx immediately inspects and commits, so run it only when you are ready to commit.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for musoyangrigor/gitx-skill and "Split messy AI changes into clean Conventional Commits"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer