atcommit

Analyze file dependencies to organize staged changes into atomic Git commits.

6|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/rtfpessoa/code-factory --skill atcommit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: atcommit
Source: https://github.com/rtfpessoa/code-factory/tree/main/git/skills/atcommit
Command: npx skills add https://github.com/rtfpessoa/code-factory --skill atcommit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents broken builds and confusing commit histories by ensuring that each commit is self-contained and logically sound, making code reviews and debugging significantly easier.

Core Features & Use Cases

  • Dependency Analysis: Automatically builds a dependency graph of all changed files.
  • Atomicity Validation: Detects and reports violations like staged files depending on unstaged ones.
  • Commit Grouping: Suggests logical groupings for commits based on dependencies and concerns.
  • Use Case: Before committing a complex feature, use this Skill to ensure all related changes are grouped correctly and that no staged file relies on an uncommitted change, preventing potential build failures.

Quick Start

Use the atcommit skill to validate and organize your staged changes into atomic commits.

Frequently Asked Questions about atcommit

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

FAQPage Schema
How do I ensure my git commits are atomic and self-contained?

To ensure git commits are atomic, you can validate staged changes by analyzing file dependencies and logical concerns, preventing broken builds. This process checks dependency closure so no staged file relies on uncommitted changes.

Why does my staged code break the build when other files are unstaged?

Staged code breaks builds when staged files depend on unstaged changes, violating commit atomicity. Dependency analysis detects this by building a graph of changed files to ensure dependency closure before committing.

Can I automatically group file changes into logical git commits?

You can automatically group file changes into logical git commits by analyzing file dependencies and logical concerns. This suggests commit groupings based on single-concern principles to simplify code archaeology and reviews.

Does this atomic commit validation require static analysis of file imports?

Yes, atomic commit validation requires static analysis of file imports and exports. This analysis builds a dependency graph to ensure dependency closure and single-concern commits within your Git workflow.

What is the best way to prevent confusing commit histories during code review?

The best way to prevent confusing commit histories is organizing staged changes into atomic, self-contained commits. Validating dependency closure ensures each commit represents a single logical concern, simplifying code reviews.

Do I need Git command-line tools to validate commit atomicity?

Yes, you need Git command-line tools to validate commit atomicity. The validation applies to Git workflows by analyzing staged code changes and static file imports to ensure safe, self-contained commits.