git-structure-commits

Structured git commits use typed trailers like Intent, Scope, and Decided-Against to encode rationale alongside changes. This machine-readable format enables agents to reconstruct context and filter history by decisions and session.

Decision archaeology uses structured commit trailers to capture reasoning and intent. By applying typed trailers such as Decided-Against and Context, you create a searchable history that prevents repeating past work.

You capture agent intent by enforcing conventional commit messages with specific trailers. Trailers like Intent, Scope, and Session are appended to commits, providing a structured memory of decisions during agent-assisted coding.

Yes, structured commits integrate into standard development workflows. The format relies on reference files to validate trailers, ensuring consistency without breaking existing git processes for standard or agent-assisted sessions.

Filtering git history by rejected options requires structured commit trailers. By enforcing a Decided-Against trailer in your conventional commits, you create a queryable archive of discarded alternatives and rationale.

You need structured commit trailers when managing agent-assisted coding sessions or rebuilding context from history. They provide a machine-readable memory of intent and decisions, enabling agents to avoid repeating work.