@ubuligan/progit-commit

A Claude Code skill that generates professional, Conventional Commits–style git commit messages by analyzing your staged diff.

Install

npx @ubuligan/progit-commit

████  █████  ███   ███  █████ ███ █   █ ███ █████ █████ 
█   █ █     █   █ █       █    █  █   █  █    █   █     
████  ████  █████ █       █    █  █   █  █    █   ████  
█  █  █     █   █ █       █    █   █ █   █    █   █     
█   █ █████ █   █  ███    █   ███   █   ███   █   █████ 

Then restart Claude Code so it picks up the new skill.

The installer links the skill into ~/.claude/skills/progit-commit (junction on Windows, symlink elsewhere; falls back to a copy if linking is denied).

Other commands:

npx @ubuligan/progit-commit --list       # show install status
npx @ubuligan/progit-commit --force      # overwrite an existing install
npx @ubuligan/progit-commit --uninstall  # remove the skill

How to use

In Claude Code, stage your changes (git add ...) and run:

/progit-commit

Claude reads the staged diff and produces a complete commit message — correct type and scope, an imperative subject, and a body explaining the why of the change.

What the skill does:

1. Collect the diff — reads git diff --cached; stops if nothing is staged.
2. Analyze intent — infers the business and technical purpose of the change.
3. Select the type — picks one of feat, fix, refactor, perf, docs, test, build, ci, chore, style.
4. Write the subject — type(scope): summary, imperative, ≤72 chars, no trailing period.
5. Write the description — bullet points covering why, what changed, and impact.
6. Add optional sections — Impact, Breaking Changes, and Testing when meaningful.
7. Add Affected Components — sorted, de-duplicated repository-relative paths (max 30).
8. Emit the final message — clean Markdown, sections in order, no fluff.

License

MIT © 2026 JAVID Salimov