Organize code changes into atomic git commits by logical intent.
npx skills add https://github.com/swtch1/dotfiles --skill commit-swtch1
Please help me install this Agent Skill. Skill: commit Source: https://github.com/swtch1/dotfiles/tree/main/.claude/skills/commit Command: npx skills add https://github.com/swtch1/dotfiles --skill commit-swtch1
This Skill helps you create well-structured and atomic git commits by grouping changes based on their underlying intent, rather than just by file. This leads to a cleaner, more understandable, and maintainable commit history.
feat:, fix:).Stage and commit the current changes using a clear, intent-based message.
High-intent search queries and answers about installing and using this skill.
To create atomic git commits based on logical intent, you need to survey staged changes, identify distinct intents, and group files into separate commits. This ensures each commit represents a single independent change for easier reverts.
The best way to write conventional commit messages for multiple changes is to separate them into focused commits. Survey the changes, identify the distinct intent of each, and apply concise imperative messages using detected formats like feat: or fix:.
Splitting mixed code changes into separate git commits requires identifying the distinct logical intent behind each modification. Plan and execute separate commits for each intent, excluding temporary files, to maintain a clean and understandable history.
Yes, this approach to version control ensures the exclusion of temporary files when staging code. It surveys your working directory to organize only meaningful modifications into atomic commits based on their underlying intent.
You need to use conventional commit formats in your development workflow when you want a standardized, readable history. The process detects existing conventional formats like feat: or fix: and guides you to apply them with concise imperative messages.
jrmatherlyGroups staged Git changes into logical commits by intent with concise messages.
glhewettCreate atomic git commits with branch validation and optional lint and test checks.
Tony363Automate Git operations with Conventional Commits and MCP integrations.
Soyio-idCreate logically scoped git commits with Conventional Commit messages from working-tree changes.