Agent skill · software engineering · aiskillstore
git-commit
Guide for breaking changes into logical, atomic commits using interactive staging. Use when committing changes that span multiple concerns, when needing to stage parts of files (hunks), when asked to create well-organized commit history, or when changes should be split into multiple commits.
Why this skill is useful
Codifies a structured approach to creating atomic commits, which the AI could infer but now doesn't have to guess.
What it needs
About 2k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Git Commit Break changes into logical, atomic commits using interactive staging. Workflow 1. Analyze all changes 2. Identify logical units (one concern per commit) 3. Stage relevant changes (whole files or hunks) 4. Commit with a good message 5. Repeat until all changes are committed Analyzing Changes Look for natural boundaries: different features, bug fixes, refactors, or config changes. Identifying Logical Commits Each commit should represent one logical change. Signs that changes belong in separate commits: Different purposes (bug fix vs feature vs refactor) Unrelated files or components Changes that could be reverted independently Separate items from a PR review or task list Common groupings: Related files implementing a single feature A bug fix with its test Rename/move operations separate from behavior changes Config or dependency changes separate from code Staging Strategies Whole files Partial files (hunk staging) Use git add -p to stage specific hunks within a file: Hunk commands: y - stage this hunk n - skip this hunk s - split into smaller hunks (if hunk contains multiple changes) q - quit, keeping already-staged hunks ? - show help Verify staged changes Commit Messages Use the commit-message skill for formatting. Key points: Conventional Commits format: type(scope): description Imperative mood ("Add feature" not "Added feature") Explain why in the body, not what (the diff shows what) Repeat After each commit: Continue staging and committing until all changes are organized into logical commits.
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/git-commit--f0acd7