LinardsLiepenieks

simplify-code

Sweeps the code changed this session for code smells (dead code, duplication, data clumps, misplaced responsibility, speculative generality) by spawning read-only sub-agents in parallel, then applies the fixes that simplify without changing behavior. One pass, not a loop; correctness belongs to harden-code. Use after a refactor or feature, or when the user says "simplify", "clean up", or "code quality pass".

structurize

Finds repetition hiding in an area (Type-3/4 clones, git co-change, shotgun-surgery scatter), researches what it is actually called (an established pattern, an algorithm, an existing package), offers the named options with what each does and why it fits, then extracts only what the user picks. Use when the user names an area and says "structurize", "standardize this", "what pattern is this", "should this be centralized", or "is there a package for this".

cleanup

Removes dead code in the area the current prompt is about, verifying every callsite of what it touches first so nothing regresses. Read the ask, find what's actually unreachable, prove it, then delete. Use when the user says "cleanup", "remove dead code", or "tidy this up".

harden-code

Iteratively hunts for crashes, data loss, and unintended contract changes in recently-changed files by running three reliability specialists in parallel (an agent team when enabled, otherwise sub-agents), re-running until no breaking findings remain. Use after a refactor or feature, or when the user says "harden", "audit for bugs", or "review for reliability".

scope-and-plan

Locates where a change will live by tracing the relevant slice of the codebase, then interrogates the plan relentlessly, one question at a time, resolving each branch of the decision tree, until you and the user reach a shared, code-grounded understanding. Use before building a feature or refactor, to stress-test a plan, or when the user says "scope this" or "plan this out".