commit

Create atomic conventional Git commits from staged and unstaged changes.

Updated May 8, 2026

Search Tags:#git #version control #commit #conventional commits #subagent #atomic changes

Ready to run

npx skills add https://github.com/mmartinsoliv/dotfiles --skill commit-mmartinsoliv

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/mmartinsoliv/dotfiles/tree/main/agents/skills/commit
Command: npx skills add https://github.com/mmartinsoliv/dotfiles --skill commit-mmartinsoliv

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns messy working-tree changes into clean, reviewable commits by enforcing one logical change per commit and a consistent conventional commit format.

Core Features & Use Cases

Atomic Change Grouping: Separates unrelated edits into distinct commits so each commit tells one clear story.
Conventional Commit Enforcement: Produces standardized commit messages with the right type, scope, and concise rationale.
Safe Commit Execution: Uses explicit file staging, pre-commit checks, and post-commit verification to avoid accidental or low-quality commits.
Use Case: When a feature change, test update, and documentation tweak are mixed together, this Skill splits them into separate commits and commits each one in sequence.

Quick Start

Use the commit skill to review the current git changes and create atomic conventional commits for each logical change.

Frequently Asked Questions about commit

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

FAQPage Schema

How do I split unstaged git changes into atomic conventional commits?▼

To split git changes into atomic conventional commits, this Skill analyzes your working tree diff and groups logically independent edits into separate commits. It enforces conventional commit messaging and executes explicit file staging without bypassing hooks.

What is an atomic commit in version control and when do I need it?▼

An atomic commit in version control contains one logical change, making history reviewable. You need it when a working tree mixes features, tests, and docs, requiring separation into distinct commits that each tell one clear story.

Can I use conventional commit formatting for both staged and unstaged changes?▼

Yes, you can apply conventional commit formatting to staged and unstaged changes. The Skill processes the working tree diff, requires explicit file selection, and generates standardized messages with the correct type and scope.

Does this approach bypass git pre-commit hooks to speed up commit execution?▼

No, this approach does not bypass git pre-commit hooks during commit execution. It performs pre-commit validation and post-commit verification on staged files to ensure safe execution and prevent accidental or low-quality commits.

What's the best way to separate mixed feature and documentation edits into distinct commits?▼

The best way to separate mixed feature and documentation edits is enforcing atomic change grouping. This Skill reviews your git diff, delegates execution of each logical change, and commits them in sequence with conventional messages.