spex-commit

Analyze git status and session transcripts to create atomic commits with decision-id trailers.

2|Updated Mar 8, 2026

Search Tags:#git #decisions #commit #requirements #code hygiene #intent #spex

Ready to run

npx skills add https://github.com/ran729/context-rot-skill --skill spex-commit

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of linking code changes to their underlying intent, ensuring every commit is traceable to specific requirements and design decisions, thereby preventing "context rot" and improving project memory.

Core Features & Use Cases

Intent Discovery: Analyzes code changes, session transcripts, and existing plans to understand the "why" behind modifications.
Knowledge Extraction: Creates structured Spex memory items (Requirements, Decisions, Policies) based on confirmed intent.
Automated Committing: Groups changes into atomic commits, each linked to a decision ID.
Use Case: After implementing a new feature, invoke this skill to automatically generate requirements, decisions, and commit messages that clearly explain the purpose and rationale of the code changes.

Quick Start

Use the spex-commit skill to commit your staged changes with traceable intent.

Frequently Asked Questions about spex-commit

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

FAQPage Schema

How do I link git commits to specific requirements and design decisions?▼

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.

What is the best way to prevent context rot and improve project memory when committing code?▼

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.

How do I generate atomic git commits with traceable commit messages automatically?▼

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.

Can I use session transcripts to discover the intent behind code changes before committing?▼

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.

Do I need a specific project memory system to commit code with 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.