commit

Drafts and confirms Git commit messages before committing staged changes.

1|Updated Dec 8, 2025
One-click install
npx skills add https://github.com/inayayousfi/myconfig --skill commit-inayayousfi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/inayayousfi/myconfig/tree/main/dotfiles/ai/.agents/skills/commit
Command: npx skills add https://github.com/inayayousfi/myconfig --skill commit-inayayousfi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing consistent, well-scoped Git commit messages is error-prone: unrelated changes get bundled in, message style drifts from project conventions, and commits happen before the user has reviewed the final wording. This Skill enforces a disciplined commit workflow that inspects the actual change set, matches repository style, and requires explicit confirmation before committing. ## Core Features & Use Cases - Change-set scoping: Inspects git status and staged diffs to determine exactly what "commit this" refers to, staging only the intended changes and refusing to bundle unrelated work. - Style-matched message drafting: Reads recent commit history to infer tense, capitalization, and prefix conventions like fix: or feat:, then drafts a subject-first message with no filler or emojis. - Confirmation-gated commits: Previews the final message in chat and asks for explicit confirmation before running git commit, then reads back the finished commit and only pushes with authorization. - Use Case: After finishing a bug fix, you say "commit this" and the Skill stages only your fix, drafts a message matching the repo's conventional-commit style, shows it for approval, and commits once you confirm. ## Quick Start Ask the assistant to commit the current changes, for example by saying "commit this", and it will stage the relevant changes, draft a message, and wait for your confirmation.

Frequently Asked Questions about commit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a good Git commit message automatically?▼

The Skill inspects your staged diff and recent commit history, then drafts a concise subject line matching the repository's existing style, including prefixes like fix: or feat:. You review and confirm the message before anything is committed.

How to commit only specific changes in Git?▼

The Skill determines what "this" refers to by checking git status and staged changes. When your session produced the changes, it stages them directly; when unrelated work exists, it stages exact paths or asks you to choose a coherent scope.

Does the commit skill push to remote automatically?▼

No, pushing requires explicit authorization. After committing, it pushes without asking only if the session already authorized it; otherwise it asks first, using git push or git push -u origin for untracked branches.

What happens if there is nothing to commit?▼

The Skill checks git diff --cached and git status first. If no changes exist, it tells you there is nothing to commit and stops rather than creating an empty or meaningless commit.

Can I change the drafted commit message before committing?▼

Yes, the Skill shows the final message in chat and asks you to confirm, request changes, or cancel. If you request changes, it redrafts the message and asks again before running git commit.