Commit

Skill Imran-ml/claude-skills/.claude/skills/commit

Reusable Claude Code configuration repository with skills, subagents, hooks, MCP setup, and examples for bootstrapping new projects.

Install

npx -y skills add Imran-ml/claude-skills --skill commit

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use this skill when the user wants to create a git commit, stage files, write a commit message, or finalize their work with a git commit. Also invoked by phrases like "commit my changes", "save to git", "git commit".

SKILL.md

1.6 KB, 326 tokens by cl100k_base, as published. Nobody here has run it

Smart Git Commit

Review staged and unstaged changes, then create a well-formatted git commit.

Steps

Run git status to see what's changed
Run git diff and git diff --cached to understand the changes
Run git log --oneline -5 to match the project's commit style
Stage relevant files with git add <files> (never use git add . blindly)
Write a commit message following Conventional Commits:
- feat: — new feature
- fix: — bug fix
- docs: — documentation
- refactor: — code restructuring (no behavior change)
- test: — adding/updating tests
- chore: — tooling, deps, config
- perf: — performance improvement
- style: — formatting, no logic change
Create the commit

Rules

Keep subject line under 72 characters
Use imperative mood: "add feature" not "added feature"
If the user provided $ARGUMENTS, use it as context or scope
Never commit .env, secrets, or settings.local.json
Warn the user before committing any sensitive-looking file

Example Messages

feat(auth): add OAuth2 login with GitHub
fix(api): handle null response from payment gateway
docs: update README with MCP setup instructions
refactor(db): extract query builder into separate module

$ARGUMENTS