Creates MEMORY.md index and 10 memory files documenting: - Scripts: context-load, start-claude, install-hooks, setup-formatters, git-status-report - Skills: /log, /reflect-logs, /reflect, /distill-best-practices, /linter Each file covers purpose, usage, how it works, and gotchas. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
1.4 KiB
1.4 KiB
skill: /distill-best-practices
Location: custom-claude-skills/skills/distill-best-practices/SKILL.md
Purpose
Cross-project best practices distillation. Reads changed memory files from all tracked projects and proposes additions, updates, or removals to claude-foundations/best-practices/. Always targets claude-foundations as output regardless of which project it's run from.
Usage
/distill-best-practices
No arguments. Interactive — presents proposals for approval before applying.
How it works
- Reads
settings.yamlfor tracked projects andbest-practices/.distill-state.jsonfor last-processed SHAs - For each project with changes since last SHA: finds changed
memory/*.mdfiles viagit diff - Maps memory files to best-practices topics (e.g.,
gotchas-k8s.md→kubernetes.md) - Classifies each potential change as ADD, UPDATE, or REMOVE
- Presents numbered proposals — waits for user approval
- Applies approved changes, updates
BESTPRACTICES.mdindex if new files created - Updates
.distill-state.jsonwith current HEADs
Part of the knowledge pipeline
/log → /reflect-logs → /distill-best-practices
Gotchas
- Generalises project-specific details: strips IPs, namespace names, hostnames — keeps principles and reasoning
- Only promotes lessons that would apply to at least one other project type
- Never auto-applies — always interactive