commit

Create atomic git commits by inspecting and grouping changes.

Updated Aug 27, 2026

Search Tags:#git #workflow #commit #code-review #version-control #atomic

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/pascalandy/dotfiles/tree/main/dot_config/opencode/skill/std-commit
Command: npx skills add https://github.com/pascalandy/dotfiles --skill commit-pascalandy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers create atomic git commits that describe a single logical change, making history easier to review and revert.

Core Features & Use Cases

Atomic commits: enforce one logical change per commit to improve traceability and rollback.
Guided workflow: analyze changes with git status and git diff, group by purpose, and commit each group separately.
Use case: when implementing a feature and fixing a small bug, create separate commits for the feature and the fix to keep history clean.

Quick Start

Stage related changes, run analysis, and commit groups with descriptive bodies. For example:

Run: git status
Run: git diff --stat
For each logical change, run: git add <files in that change>
Then: git commit -m "feat: describe the logical change" -m "Why this matters and impact"

Frequently Asked Questions about commit

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

FAQPage Schema

How do I make atomic git commits for separate logical changes?▼

To make atomic git commits, analyze changes with git status and git diff, group related files by logical purpose, stage each group with git add, and commit each group separately with a descriptive message explaining the change and its impact.

Why should I split feature work and bug fixes into separate commits?▼

Splitting feature work and bug fixes into separate atomic commits keeps version control history clean, making each logical change easier to trace, review, and revert independently without affecting unrelated code modifications.

What is the best way to inspect code changes before committing them?▼

The best way to inspect code changes before committing is to run git status to view modified files and git diff to examine the actual modifications, allowing you to group changes logically for atomic commits.

How do I write a descriptive commit body for an atomic change?▼

Write a descriptive commit body by using the git commit -m flag twice: first for a concise summary like "feat: describe the logical change", then a second message explaining why the change matters and its overall impact on the codebase.

Can I use this atomic commit workflow for repository refactoring?▼

Yes, this atomic commit workflow applies to repository refactoring, feature work, and bug fixes across any repository and collaboration context, ensuring each logical change is isolated for better traceability and rollback.

What are the limitations of enforcing atomic commits in version control?▼

Enforcing atomic commits requires manually analyzing git diff output and carefully grouping changes by purpose, which takes more time than committing all staged files at once, but produces cleaner version control history and easier rollback.