create-atomic-commits

Analyze git diffs and organize changes into atomic Conventional Commits.

Updated Dec 4, 2025
One-click install
npx skills add https://github.com/dallascrilley/dowser --skill create-atomic-commits-dallascrilley
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-atomic-commits
Source: https://github.com/dallascrilley/dowser/tree/main/skills/create-atomic-commits
Command: npx skills add https://github.com/dallascrilley/dowser --skill create-atomic-commits-dallascrilley

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Mixed working trees with unrelated feature, fix, and documentation changes are hard to commit cleanly. This Skill analyzes actual git diffs and splits them into atomic, logically grouped commits following the Conventional Commits format. ## Core Features & Use Cases - Diff-Based Analysis: Reads actual code changes (not just file names) to write precise commit messages that explain what problem each change solves. - Change Classification: Groups modifications into feat, fix, refactor, docs, style, test, perf, and chore categories, then organizes them into an independent commit series. - Chronological Timestamps: Uses the bundled git-file-timestamps script to extract file creation and modification dates for ordering commits. - Use Case: You have a working tree mixing a new dashboard feature, an API bug fix, and README updates. The Skill analyzes the diffs, recommends three separate commits with proper conventional messages, and interactively confirms each one before committing. ## Quick Start Ask the assistant to analyze my current git changes and organize them into atomic conventional commits.

Frequently Asked Questions about create-atomic-commits

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

FAQPage Schema
How do I split mixed git changes into atomic commits?▼

Analyze the actual diff content of each changed file, classify changes by type (feat, fix, docs, refactor), then stage and commit each logical group separately. This Skill automates that analysis and recommends a commit series with conventional messages.

What is the Conventional Commits format for git messages?▼

Conventional Commits use the pattern type(scope): subject, where type is feat, fix, refactor, docs, style, test, perf, or chore. The subject should describe the specific problem solved, with an optional body explaining what and why.

Can I exclude log or temporary files from commit analysis?▼

Yes. Describe the files to skip casually, such as ignore log files or skip test artifacts, and matching files are excluded from all analysis and commit recommendations. Excluded files never appear in the suggested commit series.

Does the git-file-timestamps script work on macOS and Linux?▼

Yes. The script detects the operating system and tries both macOS and Linux stat formats to get filesystem timestamps. It also queries git history for file creation and last modification dates, handling untracked and deleted files gracefully.

Why should commit messages be based on diffs instead of file names?▼

File-name-based messages like updated user service are generic and unhelpful. Diff-based messages describe the actual code change, such as adding token expiry validation, making history searchable and each commit independently understandable.