Code-Distill — Pattern Extraction Methodology for GitHub Codebases

Methodology distillation of the generic moves an agent makes when distilling code patterns on demand from a specific GitHub codebase, given a focused query. Not a per-library skill — one skill plus a thin per-library record in the shared knowledge graph (/knowledge/libraries/), because 90% of the work is the same regardless of which repo.

This is the dynamic light sibling of your static code-atlas distillations: opencode-ts, openai-codex-rust-patterns, nextjs-ppr-patterns. Those skills are heavy curated outputs — they distilled patterns from a single repo ahead of time. This skill is the on-demand alternative: when no static skill exists for the library yet, point at the repo and let the methodology run.

When to Apply

Use this skill when:

• The user asks "how does <library> implement <feature>?" and points at (or names) a real GitHub repo
• The query is focused on a single subsystem (design system, composition, state, error handling, effects, build, routing) — not "what is this whole codebase?"
• No static code-atlas skill exists for the library yet (or the existing one is stale)
• An ad-hoc invocation looks like /distill <library> <query> or "show me X in repo Y" in natural language
• The library has too small a surface area, or too short a lifespan, to justify authoring a full static code-atlas distillation

This skill is NOT for: