atomic-commits

Create semantic atomic commits following the Conventional Commits specification.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/paulovictor237/PeveAgent --skill atomic-commits-paulovictor237
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: atomic-commits
Source: https://github.com/paulovictor237/PeveAgent/tree/main/.agents/skills/atomic-commits
Command: npx skills add https://github.com/paulovictor237/PeveAgent --skill atomic-commits-paulovictor237

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developers often create commits that combine multiple unrelated changes, leading to unclear history and difficult rollbacks. This Skill enforces atomic, well‑structured commit messages based on the Conventional Commits standard.

Core Features & Use Cases

  • Automated analysis of staged and unstaged changes to suggest appropriate commit type and scope.
  • Interactive guidance that proposes commit messages and asks for confirmation before committing.
  • Multi‑commit handling allowing complex changes to be split into separate, focused commits.

Quick Start

Ask the atomic‑commits skill to analyze your current changes and create a conventional commit for them.

Frequently Asked Questions about atomic-commits

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

FAQPage Schema
How do I create conventional commits automatically from my git changes?

To create conventional commits automatically, this Skill analyzes your staged and unstaged git changes to determine the commit type and scope, then proposes a properly formatted message for your confirmation before executing the commit.

What is the best way to split multiple unrelated changes into atomic commits?

The best way to split changes into atomic commits is using multi-commit handling, which analyzes complex mixed changes and separates them into focused, individual commits with appropriate semantic messages for each distinct update.

Does this automated commit tool require access to the git CLI?

Yes, this automated commit tool requires access to the git CLI and file system for diff analysis, along with the ability to execute bash commands for staging changes and committing them.

Can I review and edit the suggested commit message before it is committed?

Yes, you can review the suggested message because the Skill provides interactive guidance, proposing a semantic commit message and asking for your explicit confirmation before executing the final git commit.

How does diff analysis determine the correct scope for a conventional commit?

Diff analysis determines the correct scope by examining your staged and unstaged file changes, evaluating the modifications to suggest an appropriate commit type and scope that aligns with the Conventional Commits specification.