spex-commit

To link git commits to requirements and design decisions, you can automate the process by analyzing session transcripts and existing plans to capture intent, clustering changes into atomic commits, and generating traceable messages with decision-id trailers.

Preventing context rot requires ensuring every commit is traceable to specific requirements. By extracting structured memory items from confirmed intent during the commit process, you capture the rationale behind modifications and maintain project memory.

Generating atomic git commits with traceable messages involves analyzing your git status and code changes, grouping related modifications into logical clusters, and linking each cluster to a decision ID to explain the code's purpose.

Yes, you can use session transcripts to discover intent before committing. By analyzing session transcripts alongside code changes and existing plans, the system understands the why behind modifications and creates structured requirements based on confirmed intent.

Committing code with intent relies on a project memory system to store structured Spex memory items like requirements and decisions. This system captures the underlying intent of modifications to prevent context rot and ensure commits are traceable.