atomic-git-commit

Analyze git status and diff to group changes into atomic conventional commits.

4|1|Updated Apr 4, 2024
One-click install
npx skills add https://github.com/maraxen/praxis --skill atomic-git-commit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: atomic-git-commit
Source: https://github.com/maraxen/praxis/tree/main/.agent/skills/atomic-git-commit
Command: npx skills add https://github.com/maraxen/praxis --skill atomic-git-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviewing uncommitted changes and turning them into meaningful, atomic commits can be error-prone and time-consuming. This skill guides you to segment work into logical units and apply Conventional Commits.

Core Features & Use Cases

  • Analyze uncommitted changes with git status and git diff to understand scope.
  • Group related changes into atomic commits that reflect features, fixes, or chores.
  • Generate clear, conventional commit messages and verify the final state before pushing.

Quick Start

Review your current changes, group them into logical units, and commit each group with a conventional message.

Frequently Asked Questions about atomic-git-commit

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

FAQPage Schema
How do I split uncommitted git changes into logical commits?

Atomic commits involve grouping related file changes into a single logical unit before staging. This practice ensures each git commit represents a specific feature, fix, or chore, making code review and version history significantly easier to track.

How do I generate conventional commit messages for multiple file changes?

You generate conventional commit messages by categorizing grouped changes into types like features or fixes. The workflow analyzes the grouped state and applies conventional-commit style messaging to produce clear, standardized git commit descriptions.

What is the best way to review git diff before committing changes?

The best way to review git diff is to analyze the scope of uncommitted changes across multiple files. By understanding the full state of modifications, you can verify the final state and group related changes into logical commit units.

Does atomic git commit work with standard version control workflows?

Yes, it supports standard version control workflows by applying end-to-end governance over the commit process. It analyzes state, groups changes, and generates conventional commit messages to fit seamlessly into existing development workflows.

Why use conventional commits for atomic git commits?

Conventional commits provide a standardized format for atomic git commits, categorizing them as features, fixes, or chores. This structured messaging enables end-to-end governance, making it easier to verify the final state before pushing to version control.