Stage and commit changes with conventional messages and logical grouping.
npx skills add https://github.com/ebkn/dotfiles --skill commit-ebkn
Please help me install this Agent Skill. Skill: commit Source: https://github.com/ebkn/dotfiles/tree/main/root/.claude/skills/commit Command: npx skills add https://github.com/ebkn/dotfiles --skill commit-ebkn
Replaces ad-hoc, monolithic commits with small, well-scoped conventional commits so history is easier to review, revert, and understand. It reduces reviewer friction by ensuring each change is grouped by scope and intent and documented with a concise subject and optional explanatory body.
Run the commit skill to inspect diffs, split unrelated changes into logical staged sets, and create conventional commit messages following the repository style.
High-intent search queries and answers about installing and using this skill.
To split mixed changes into separate conventional commits, inspect the working diffs and recent logs to identify logical boundaries, then stage related files or hunks into distinct commits with concise, scope-based messages. This ensures history is easier to review and revert.
You stage related files or hunks into separate commits by using git diff to inspect changes, grouping related edits logically, staging them with git add, and committing with conventional messages that classify the change by scope and intent.
Yes, this conventional commit approach works with local git repositories where developers have read and write access, the ability to run git status, diff, log, add, and commit, and apply human judgment to group hunks and compose messages.
Use conventional commits instead of monolithic commits to ensure each change is grouped by scope and intent, producing a concise, reviewable history that is significantly easier to review, revert, and understand when examining project evolution.
The best way to group simultaneous updates to different config files is to split them into separate commits classified by scope and intent, such as isolating zsh, vim, and tmux configuration changes to produce a clearer, more reviewable history.
You should not use conventional commits for staging changes if your local repository lacks git read and write access, or if the environment cannot execute git status, diff, log, add, and commit commands required to inspect diffs and group hunks.
TakSungTrack Git repository changes and summarize status, commits, and diffs.
VYRE-StudiosCommit staged changes, push the branch, and open a pull request via GitHub CLI.
pekralStandardize Git branching strategies and complex version control operations.
jellyrockAutomate secure, convention-compliant Git commits with pre-commit security checks.
