grill-me-code-style-reviewlisted

Review a large changeset (a branch, working tree, or PR — tens to hundreds of files) against a repo's code-style.rules.json so the user can trust it WITHOUT reading every diff, and LEARN the architecture from a short teaching report instead. Runs Biome (+ its grit plugins) to auto-fix the mechanical/structural channels across all files, then fans out sub-agents over the diff to check only the judgment-channel rules + the user's original intent, and returns a deviations-only report that opens with a layer/flow map of what changed and teaches the "why" behind each finding. Use when reviewing/auditing a big diff, a PR, or an AI-generated changeset, or the user says "review this", "can I trust this diff", "audit these changes". To coach while building, use grill-me-code-style-coach; to create the ruleset, grill-me-code-style.
YosefHayim/dufflebag · ★ 0 · Code & Development · score 66

Install: claude install-skill YosefHayim/dufflebag

<what-to-do> I changed a lot of files and I want to **trust the batch without reading every diff** — and come out **understanding what changed**, not alienated from my own code. So collapse the diff into a short, teaching report: let the machine carry the mechanical load, and spend judgment (and my attention) only where a machine can't. **Read first:** the repo's `code-style.rules.json` (each rule's `verify` command + exemplars), `CODE-STYLE.md`, `PROJECT.md`/`CONTEXT.md`, and **my original prompt/intent** (ask me for it if you don't have it — Tier 3 checks the diff *did what I asked* and flags scope creep). No ruleset? Offer `grill-me-code-style(-with-docs)` first. **Scope the diff** (ask if unclear): `git diff <base>...HEAD` (branch/PR), the uncommitted working tree, or a named PR. That file list is the review surface. </what-to-do> <supporting-info> ## The three tiers — cheapest enforcement first Walk **every** rule in the ruleset by its `verify` command. Most never reach me: 1. **Tier 1+2 — deterministic, whole-tree, auto-fix (every rule with a real `verify` command).** Run the repo's gate: `biome ci .` / `lint:fix`, then `verify` (biome + tsc + tests + build), plus any repo style script a rule points at (e.g. `pnpm style`). Those rules **all** run here — across all files at once. **Auto-fix everything safe**, re-run to green. I read **nothing** for this tier. Never weaken a rule/test to go green — fix the code. 2. **Tier 3 — judgment, fanned out over