git-atomic-commit

Group repository changes into atomic conventional commits by file type.

5|Updated Dec 9, 2025

Search Tags:#automation #git #version-control #conventional-commit #atomic-commit #scope-management

Ready to run

npx skills add https://github.com/arisng/github-copilot-fc --skill git-atomic-commit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-atomic-commit
Source: https://github.com/arisng/github-copilot-fc/tree/main/skills/git-atomic-commit
Command: npx skills add https://github.com/arisng/github-copilot-fc --skill git-atomic-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams avoid messy, multi-change commits by analyzing repository changes, grouping them into logical atomic units, and guiding the user to craft conventional commit messages that reflect each change.

Core Features & Use Cases

Atomic grouping: Assigns a distinct commit per changed file group based on project-specific mappings and ensures different types are committed separately.
Conventional commits guidance: Generates and enforces conventional commit messages aligned with the file-type mapping.
Workflow guidance: Provides a step-by-step process to review changes, stage files, plan commits, and apply them in a buildable order.

Quick Start

Start by reviewing the planned atomic commits, then apply them to your working branch following the guided steps.

Frequently Asked Questions about git-atomic-commit

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

FAQPage Schema

How do I split multi-file git changes into atomic conventional commits?▼

Splitting multi-file git changes into atomic conventional commits requires analyzing repository changes, grouping them into logical units by file-type mapping, and guiding the user through a step-by-step workflow to stage and apply commits separately.

What is an atomic commit in version control?▼

An atomic commit in version control is a single, logically grouped change that ensures different types of modifications are committed separately, keeping the repository history clean and buildable throughout the workflow.

How do I generate conventional commit messages for refactoring work?▼

Generating conventional commit messages for refactoring work involves analyzing the repository changes, applying a per-file type mapping, and enforcing commit messages that align with the specific type of each logical change group.

Can I automate git commit grouping for feature work across software projects?▼

Yes, you can automate git commit grouping for feature work across software projects by analyzing the changes, assigning a distinct commit per changed file group, and separating commits by type based on project-specific mappings.

What is the best way to manage git scope for multi-file edits?▼

The best way to manage git scope for multi-file edits is to analyze the repository changes, group them into logical atomic units based on file-type mappings, and apply them in a buildable order through a guided commit workflow.