Stages conversation-modified files and invokes a git commit sub-agent.
npx skills add https://github.com/pokutuna/dotfiles --skill commit-pokutuna
Please help me install this Agent Skill. Skill: commit Source: https://github.com/pokutuna/dotfiles/tree/main/claude/skills/commit Command: npx skills add https://github.com/pokutuna/dotfiles --skill commit-pokutuna
git add, ignoring unrelated changes in the working tree. - Staging Verification: Runs git status --short to confirm everything intended is staged, catching failed pathspecs and partially staged renames before committing. - Delegated Committing: Invokes the git-commit-agent skill with a brief summary of what was staged and why, so the commit message reflects the conversation's intent. - Use Case: After a coding session where you edited three source files, ask to commit the changes and the Skill stages exactly those files and produces a commit without touching unrelated work. ## Quick Start Ask the assistant to commit the changes made in this conversation, optionally passing extra arguments for the commit.High-intent search queries and answers about installing and using this skill.
Invoke the commit skill, which stages only the files modified during the conversation using git add and then calls the git-commit-agent skill to create the commit. Unrelated changes shown in git status are left unstaged.
It runs git status --short after staging to confirm everything intended is fully staged. A failed pathspec aborts the whole git add, and a rename with later unstaged edits shows as RM, so anything missing is re-added before committing.
The Skill tool path preserves this conversation's context about what was staged and why. The Agent tool path re-judges staging without that context, which can lead to incorrect staging decisions.
Yes. Any user-provided arguments are forwarded to the git-commit-agent skill along with a one-to-two line summary of what was staged and why.
It relies on conversation history to know which files were touched, so if that history is insufficient it may need to inspect git state directly. It also depends on the separate git-commit-agent skill being available.
jboothomasLoad repository-specific Qodo coding standards before code changes.
santychuycomAnalyze diffs, create atomic conventional commits, push, and open pull requests.
kirvinStage Git changes and create conventional commit messages with preflight checks.
laicluseGroups all uncommitted git changes into logical commits with descriptive messages.