commit

Stage and commit a single logical change after three-gate manual approval.

1|1|Updated Feb 15, 2026

Search Tags:#git #workflow #commit #code-review #version-control #atomic-commit

Ready to run

npx skills add https://github.com/lithiumtoast/hearthportal --skill commit-lithiumtoast

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/lithiumtoast/hearthportal/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/lithiumtoast/hearthportal --skill commit-lithiumtoast

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Stage a single atomic change from the working tree and commit it only after explicit user approval. Enforces a three-gates workflow (slice approval, staged-diff verification, and commit message approval) and formats messages according to Conventional Commits with a Linus-style body. It never pushes to a remote.

Core Features & Use Cases

One commit = one logical change.
Three gates: slice, staged-diff, and message approval; never advance without explicit user consent.
Conventional Commits subject and Linus-style body; no pushes unless explicitly requested.
Applies to incremental changes, code reviews, and small feature work in local/git workflows.

Quick Start

Provide a single slice proposal, obtain explicit user approval, then stage and commit the approved slice with a conventional subject and Linus-style body.

Frequently Asked Questions about commit

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

FAQPage Schema

How do I stage and commit a single atomic change in git?▼

Atomic commits in git isolate a single logical change by staging it separately and committing only after explicit manual approval. This ensures one commit equals one logical change, keeping version control history clean and reviewable.

What is a three-gate workflow for git commits?▼

A three-gate git commit workflow requires explicit approval at three stages: slice selection, staged-diff verification, and commit-message approval. The process stops and waits for user consent at each gate before advancing to the next phase.

How do I format git commit messages using Conventional Commits and a Linus-style body?▼

Formatting git commits with Conventional Commits and a Linus-style body involves enforcing a structured subject line and a detailed body. The workflow applies this format during the commit-message approval gate before finalizing the change.

Can I use an atomic commit workflow for code reviews and incremental changes?▼

Yes, an atomic commit workflow applies directly to code reviews, incremental changes, and small feature work in local git workflows. It isolates individual changes, making them easier to review and track throughout a development session.

Does this git commit workflow automatically push to a remote repository?▼

No, this git commit workflow never pushes to a remote repository unless explicitly requested. It strictly stages and commits local changes, and it also refrains from amending existing commits without direct user instruction.