Reviews staged changes and creates a conventional git commit.
npx skills add https://github.com/KMakayee/playbook --skill commit-kmakayee
Please help me install this Agent Skill. Skill: commit Source: https://github.com/KMakayee/playbook/tree/main/.claude/skills/commit Command: npx skills add https://github.com/KMakayee/playbook --skill commit-kmakayee
This Skill prevents sloppy or incomplete git commits by forcing a quick staged-review loop, handling untracked files intentionally, and guiding you to write a clean conventional commit message before creating and pushing the commit.
git status and both unstaged (git diff) and staged (git diff --staged) context so you commit with confidence.type: subject message (subject under 72 characters) derived from the staged diff.tasks/errors.md via the repo reflection template.Run the commit skill to review your staged changes, draft a conventional commit message, create the commit, and push it to your current branch.
High-intent search queries and answers about installing and using this skill.
A conventional commit message is generated by reviewing your staged diff and extracting a concise type: subject format, keeping the subject under 72 characters. The skill drafts this automatically before committing to your current branch.
Untracked files are handled intentionally by detecting them via git status and prompting you to decide which ones to include. This prevents accidentally leaving necessary files out of your git commit before pushing.
The best way to review changes before a git push is to check both git diff for unstaged edits and git diff --staged for staged edits. This ensures you commit exactly what you intend to the current branch.
Yes, you can automate git commit and push by running the skill after staging files. It reviews the changes, creates the commit with a conventional message, and pushes the result directly to your current branch.
A conventional commit workflow handles git errors and reflection logs by recording noteworthy learnings into tasks/errors.md after pushing. This ensures development errors are tracked for future reference.
Yes, you need to manually stage files using git add before running the automated commit. The skill checks git status to show staged and unstaged context but expects you to stage changes intentionally first.
MohibShaikhStage changes, create a contextual commit message, and push the current branch.
maslennikov-igGenerate Keep a Changelog–compliant Markdown sections from git commits, plan files, or manual entries.
trevin-jRun tests, linters, and static analysis before committing with Conventional Commits.
paywherebSquash all branch commits into one via interactive git rebase.