distill-module

Roll up MODULE-tagged Decision blocks from git commit bodies into .claude/decisions/<id>.md.

4|Updated May 5, 2026

Search Tags:#git #documentation #workflow automation #knowledge management #decision distillation #module governance #consensus snapshots

Ready to run

npx skills add https://github.com/mthli/skills --skill distill-module

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: distill-module
Source: https://github.com/mthli/skills/tree/main/distill-module
Command: npx skills add https://github.com/mthli/skills --skill distill-module

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

distill-module turns scattered MODULE-tagged Decision blocks from git commit messages into a single, readable current-consensus snapshot for one module.

Core Features & Use Cases

Layered knowledge loop: derives an editable “current consensus” file from the immutable decision history in git log.
Deterministic snapshot structure: organizes results into Active decisions (with stable D-n IDs) and a Superseded appendix.
Guardrails for correctness: reuses existing decision IDs when a prior snapshot exists and avoids rewriting history by requiring explicit user approval before writing.

Quick Start

Run distill-module when you explicitly want to consolidate the recent MODULE-tagged decisions for a specific module into .claude/decisions/<id>.md.

Frequently Asked Questions about distill-module

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

FAQPage Schema

How do I consolidate git commit decisions into a module snapshot?▼

To consolidate git commit decisions into a module snapshot, this Skill extracts MODULE-tagged Decision blocks from git log bodies and rolls them into a current-consensus snapshot at .claude/decisions/<id>.md. It requires explicit user approval before writing the file.

What is the best way to maintain decision history for a specific module?▼

Maintaining decision history for a specific module involves deriving an editable current consensus file from the immutable decision records stored in your git log. This approach organizes active decisions with stable D-n IDs and archives superseded ones in an appendix.

When should I refresh module decision state from git commit messages?▼

You should refresh module decision state from git commit messages after completing a coherent chunk of work or when enough new decisions have accumulated since your last distillation. This ensures the snapshot accurately reflects the current consensus.

Do I need a specific file to validate module IDs before distilling decisions?▼

Yes, you need a valid .claude/MODULES.md file to verify module IDs before distilling decisions. The Skill reads this file to extract and validate Decision fields from the git log and ensure the target module is valid.

How does decision distillation handle existing snapshots and ID stability?▼

Decision distillation handles existing snapshots by preserving D-n ID stability through SUPERSEDES chains against any current destination file. This prevents rewriting history by reusing existing decision IDs and properly archiving superseded entries.

Can I automate writing consensus snapshots without user approval?▼

No, you cannot automate writing consensus snapshots without user approval. The Skill gates all file writes behind explicit user confirmation to avoid rewriting history and ensure the generated snapshot is intentionally reviewed before saving.