Piggy-

Audit the whole repo for over-engineering. A ranked list of what to delete, simplify, or replace with stdlib or native features.

Harvest every piggy: shortcut comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.

Show piggy measured impact as a scoreboard: less code, less cost, more speed, from the benchmark medians. One-shot display.

Quick reference for piggy's modes, skills, and commands. One-shot display.

Review a diff for over-engineering. Finds what to delete: reinvented stdlib, needless deps, speculative abstractions. One line per finding.

Lazy senior dev mode for any coding task (write, refactor, fix, review): YAGNI, stdlib first, no unrequested abstractions. Not for non-coding requests.

Whole-repo audit for over-engineering. Like piggy-review, but scans the entire codebase instead of a diff: a ranked list of what to delete, simplify, or replace with stdlib/native equivalents. Use when the user says "audit this codebase", "audit for over-engineering", "what can I delete from this repo", "find bloat", "piggy-audit", or "/piggy-audit". One-shot report, does not apply fixes.

Show the lazy piggy version and the verbose from-scratch version of the same code side by side, so the tradeoff is visible instead of taken on faith. Use when the user says "compare versions", "show me both ways", "piggy compare", "/piggy-compare", or "what would this look like without piggy".

Harvest every `piggy:` comment in the codebase into a debt ledger, so the deliberate shortcuts and deferrals piggy leaves behind get tracked instead of rotting into "later means never". Use when the user says "piggy debt", "/piggy-debt", "what did piggy defer", "list the shortcuts", "piggy ledger", or "what did we mark to do later". One-shot report, changes nothing.

Explain why a simplification was chosen instead of the more elaborate alternative, for the last piggy edit or a pointed-to piece of code. Teaching tool, not a review. Use when the user says "explain this", "why so simple", "piggy explain", "/piggy-explain", "why not use a class here", or asks what a piggy: comment means.

Show piggy's measured impact as a compact scoreboard: less code, less cost, more speed, from the benchmark medians. One-shot display, not a persistent mode, and not a per-repo number. Trigger: /piggy-gain, "piggy gain", "what does piggy save", "show piggy impact", "piggy scoreboard".

Quick-reference card for all piggy modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /piggy-help, "piggy help", "what piggy commands", "how do I use piggy".

Code review focused exclusively on over-engineering. Finds what to delete: reinvented standard library, unneeded dependencies, speculative abstractions, dead flexibility. One line per finding: location, what to cut, what replaces it. Use when the user says "review for over-engineering", "what can we delete", "is this over-engineered", "simplify review", or invokes /piggy-review. Complements correctness-focused review, this one only hunts complexity.

Score a function or file's complexity 1-10 and show before/after when piggy simplifies it. Quick gut-check number, not a full review. Use when the user says "score this", "how complex is this", "piggy score", "/piggy-score", or "rate this function".

Forces the laziest solution that actually works, simplest, shortest, most minimal. Channels a senior dev who has seen everything: question whether the task needs to exist at all (YAGNI), reach for the standard library before custom code, native platform features before dependencies, one line before fifty. Supports intensity levels: lite, full (default), ultra. Use on ANY coding task: writing, adding, refactoring, fixing, reviewing, or designing code, and choosing libraries or dependencies. Also use whenever the user says "piggy", "be lazy", "lazy mode", "simplest solution", "minimal solution", "yagni", "do less", or "shortest path", or complains about over-engineering, bloat, boilerplate, or unnecessary dependencies. Do NOT use for non-coding requests (general knowledge, prose, translation, summaries, recipes).

Generate the smallest runnable test that would fail if the lazy solution broke — one check, no framework or fixtures unless the repo already uses one. Use when the user says "test this", "piggy test", "/piggy-test", or "write a check for this".