distill-devfile

Reconciles dev-log entries into dev-file architecture volumes and updates verification stamps.

3|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/langgenius/due-date-hq-jwl --skill distill-devfile-langgenius
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: distill-devfile
Source: https://github.com/langgenius/due-date-hq-jwl/tree/main/.claude/skills/distill-devfile
Command: npx skills add https://github.com/langgenius/due-date-hq-jwl --skill distill-devfile-langgenius

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Architecture documentation drifts out of sync with code as development progresses. This Skill folds dated dev-log entries and their underlying commits back into the dev-file volumes that serve as the project's current-truth docs, so AI agents and humans can keep trusting them. ## Core Features & Use Cases - Delta-only processing: Reads each volume's 最后核对 stamp and processes only dev-logs and commits newer than that date, keeping regular runs cheap. - Routing map: Directs each log to the correct volume (tech stack, data model, security, DevOps, and more) based on topics and proving code paths. - Parallel per-volume agents: Spawns one subagent per affected volume that verifies every claim against source code before editing, then bumps the verification stamp. - Hygiene sweep and landing: Flags naming violations and stale design docs, then formats, validates with CI checks, and lands the changes as a single commit and pull request. - Use Case: After a sprint week, ask for the weekly docs pass; the Skill reconciles all new dev-logs into volumes 00–08, 11, and 12 while leaving historical snapshot volumes untouched. ## Quick Start Ask the AI to run the weekly dev-file distillation pass to fold recent dev-log entries back into the architecture volumes.

Frequently Asked Questions about distill-devfile

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

FAQPage Schema
How do I keep architecture documentation in sync with code changes?

Run a distillation pass that reads each documentation volume's last-verified stamp, collects dev-logs and commits newer than that date, and folds verified changes back into the volumes. Each claim is checked against source code before editing, and the stamp is bumped afterward.

How does the dev-file distillation routing map work?

Each dev-log is routed to one or more volumes based on its topics and proving code paths, such as migrations to the data-model volume or CI workflow changes to the DevOps volume. A single log can update multiple volumes.

Does the distillation pass process the entire documentation history each time?

No. It processes only the delta since each volume's 最后核对 stamp, so regular runs stay cheap. Missed weeks self-correct because the processing window simply grows until the next run.

Can the distillation skill update historical snapshot volumes?

No. Volumes 09 and 10 are bannered historical snapshots and are never updated or re-stamped. Only volumes 00 through 08, 11, and 12 participate in the distillation pass.

What happens when a dev-log claim contradicts the actual code?

Code is treated as truth and dev-logs as leads. Each per-volume agent verifies every claim against the cited source path before writing, and uncertain items are flagged in the final report instead of being written into the volume.