# git-atomic-commits

> Atomic commits discipline: one commit = one logical idea — how to split a mixed working tree, when to batch, and why atomicity matters more in a human-AI team (the message FORMAT is the separate conventional-commits flow)

A community documentation of nothing it declares, published by org.vibevm.world, in en.
Read it at /doc/org.vibevm.world/git-atomic-commits/1.0.0/. Rendered 2026-09-12.

Atomic commits discipline: one commit = one logical idea — how to split a mixed working tree, when to batch, and why atomicity matters more in a human-AI team (the message FORMAT is the separate conventional-commits flow)

## For agents

- [Boot snippet](/doc/org.vibevm.world/git-atomic-commits/1.0.0/boot-snippet/): `org.vibevm.world/git-atomic-commits@1.0.0` contributes a boot snippet: text that a session reads before it starts work, placed into the project's generated boot lane by `vibe install`. It is not read on this page — it is read by the agent. (1 min · user, agent)

## Pages

- [Package manifest](/doc/org.vibevm.world/git-atomic-commits/1.0.0/manifest/): What `org.vibevm.world/git-atomic-commits@1.0.0` declares about itself. Everything on this page is the package's own manifest, read and shown — nothing here is an opinion about the package. (1 min · user, dev)