# Commit (/academy/commit)



A commit is a field note stapled to the page.

[Git](/academy/git) already has the drawing. The commit adds the caption: what changed, and why you thought that was a good idea at 1 a.m. Without the caption, you have a thick sketchbook and no idea which page still boots.

The files are the evidence. The message is the index.

**Write the caption for the teammate who forgot**

That teammate is you, after the demo. "wip" is a shrug you mailed yourself. "Add magic-link login" is a map. One opens twenty files. The other points at the door.

Small pages beat one giant page at dawn. If the demo dies, you want the note from before the explosion, not "stuff" covering twelve files. A [branch](/academy/branch) full of tiny commits is easier to walk than one blob that also "fixed cors, maybe."

Agents via [MCP](/academy/mcp) or the plugin will happily drop notes as they go — if you let the trail exist. One commit at the end of the night is how you lose the morning.

**The trail is the weekend**

Scroll the log and you can read the hackathon: scaffold from `npx create-hackhaton-space-stack@latest`, first working boot, the [pull request](/academy/pull-request) you opened because you were about to touch `main`. Nobody's memory survives that weekend. The log does.

A good message is not decoration. It is how you find the page when the room is on fire.

**What this unlocks**

A trail you can walk backward. One bad hour does not eat the whole night.

Caption the page. Then you can find it.