commit

Guide staging and formatting of atomic conventional Git commits.

Updated Feb 19, 2026

Search Tags:#git #code review #version control #commit #conventional commits #atomic commits

Ready to run

npx skills add https://github.com/sustinbebustin/.dotfiles --skill commit-sustinbebustin

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/sustinbebustin/.dotfiles/tree/main/home/.claude/skills/commit
Command: npx skills add https://github.com/sustinbebustin/.dotfiles --skill commit-sustinbebustin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you create clean, meaningful Git commits by enforcing a combination of atomic commit principles and the conventional commit message format, ensuring clarity, reversibility, and better project history.

Core Features & Use Cases

Atomic Commits: Guides users to make one logical change per commit.
Conventional Commits: Enforces a standardized message format (<type>(<scope>): <description>).
Use Case: When you've made several distinct changes (e.g., a bug fix and a new feature), this skill helps you stage and commit them separately with appropriate messages, rather than lumping them together.

Quick Start

Use the commit skill to stage and commit your current changes following the conventional commit format.

Frequently Asked Questions about commit

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

FAQPage Schema

How do I write conventional commit messages for atomic Git commits?▼

Atomic Git commits isolate one logical change per commit, ensuring your version control history remains clear, reversible, and maintainable by preventing unrelated bug fixes and features from being lumped together.

How do I stage and commit separate changes independently in Git?▼

To stage and commit separate changes independently in Git, you isolate specific modified files or hunks for staging, then commit each logical change separately with its own structured conventional commit message.

When do I need to use the conventional commit format for my changes?▼

You need the conventional commit format for software development workflows requiring clear, traceable, and maintainable version control history, applying structured types, scopes, descriptions, bodies, and footers for enhanced readability and automation.

Does this commit skill work for splitting multiple distinct changes into separate commits?▼

Yes, this commit skill works for splitting multiple distinct changes by guiding you to stage and commit them separately with appropriate messages, rather than lumping a bug fix and a new feature together.

What is the best way to structure a Git commit message for project maintainability?▼

The best way to structure a Git commit message for maintainability is applying the conventional commit format with types, scopes, descriptions, bodies, and footers, ensuring clarity and structured project history.