Converts session decisions into durable Fux memory and ADR entries.
npx skills add https://github.com/arpitarya/fux --skill fux-distill-arpitarya
Please help me install this Agent Skill. Skill: fux-distill Source: https://github.com/arpitarya/fux/tree/main/archive/v0.1/fux/data/skills/distill Command: npx skills add https://github.com/arpitarya/fux --skill fux-distill-arpitarya
memory and adr entries in the Fux index so they remain searchable and reusable. ## Core Features & Use Cases - Decision capture: Turns durable conclusions into typed entries (memory, adr, rule) with proper frontmatter, scope, and code_refs. - Capture queue integration: Reads $FUX capture --list to seed distillation from files that changed during the session, split into uncovered and governed candidates. - Human-confirmed workflow: Proposes 1–5 candidate entries for user approval before writing, then scaffolds, links, rebuilds, and lints the index. - Use Case: After a session where the team chose avg-cost over FIFO for inventory valuation, run the distill flow to create an adr entry recording the decision, its context, and consequences, linked to the relevant code. ## Quick Start Ask the assistant to run /fux distill to review this session and propose durable memory or ADR entries for confirmation.High-intent search queries and answers about installing and using this skill.
Run the distill workflow, which reviews the session, proposes 1–5 candidate memory or ADR entries, and asks for confirmation before writing. Confirmed entries are scaffolded with the Fux CLI, linked to related entries, and committed to the .fux index.
Capture durable knowledge: stated user preferences, decisions with a rationale, and discovered rules or gotchas tied to code. Skip transient narration, debugging dead-ends, facts already in git history, and secrets or machine-specific paths.
No. Distillation is a judgement call, so the skill always proposes candidate entries first and waits for user confirmation or trimming before scaffolding anything. Only the confirmed $FUX new calls touch disk.
A memory entry records observations, preferences, or feedback with Observation/Why/How to apply sections. An ADR records a decision with Decision/Context/Consequences sections. Both support scope (personal vs shared) and code_refs linking.
The lint checks enforce quality: a memory entry without a Why section is considered noise, and code-bound rules need real code_refs. Fix these findings after $FUX build so the new entries meet the index's durability standards.
StiensGate928Update HANDOFF.md with current Git status, changed files, and next steps.
fredmilhomeDistill the current conversation into a structured note for future reference.
Impractical-InstrumentsDistill architectural decision records into structured rule-based documentation.
chris-prenerFiles, supersedes, audits, and indexes Architecture Decision Records in docs/adr/.