distilllisted

Pattern mining — surface the codebase's recurring implicit conventions (error handling, construction, data access, naming, test shape…), verdict each as BLESS / UNIFY / BAN / DEEPEN with cited occurrences, then install the verdicts where agents actually read them: project rules, CONTEXT.md, reference examples. Makes the implicit explicit so generated code copies the best pattern in the repo instead of the most frequent one. TRIGGER when: the user wants to extract/codify the codebase's conventions, "make the code consistent", "what patterns do we have", "turn how we do X into a rule", or after inheriting a codebase whose house style exists only in the code. DO NOT TRIGGER when: hunting rot/shallow modules (use /arch-health), applying cleanups to a diff (use /refactor), executing an already-decided mass migration (use /sweep), or writing the initial profile for a fresh project (use /bootstrap).
mik2win/foureyes · ★ 2 · AI & Automation · score 79

Install: claude install-skill mik2win/foureyes

# Distill Patterns: $ARGUMENTS `$ARGUMENTS` optionally scopes the mining to a subtree or a dimension ("error handling in the API layer"); empty = the whole codebase, all dimensions below. ## Principle Every codebase teaches by example — and its next contributor is an agent that learns the house style from whatever code it happens to read. If three error-handling styles coexist, generated code picks one at random; if the dominant example is bad, **every generated line copies the rot forward**. Consistency isn't aesthetics: it's the difference between a codebase that compounds and one that decays with each addition. This skill closes the loop: **mine** the recurring patterns actually present, **verdict** each one deliberately instead of letting frequency decide, and **install** the verdicts where they change behavior — always-on rules, `CONTEXT.md`, reference examples. The kit's rule packs carry the *stack's* conventions; this skill extracts the *project's own*, which no pack can know. It decides and codifies. Code changes (unification, deepening) route out. ## Phase 0 — Load profile 1. Read `.claude/PROJECT.md` — **Architecture**, **Conventions**, **Plans location**. Missing or `TEMPLATE` → fall back to the root `CLAUDE.md` (always in context) when it carries those facts, proceeding on it and noting you're running without a kit profile; only if *neither* has them, **STOP**, run `/bootstrap` first. 2. Read the installed `.claude/rules/*` (generic + stack packs)