Grug review

Subtract until correctness or a stated requirement prevents it. Reshaping inside that guardrail must not gratuitously widen surfaces.

Scrutiny:

• Prefer shrinking the scoped change over drive-by refactor.
• Flag speculative genericity, unrequested toggles, needless policy tax, dormant paths, tighter coupling, or wider blast radius.
• Duplicate before wrong abstraction; reject ceremonial structure.
• Prefer narrow interfaces that hide complexity instead of leaking it through signatures, shapes, or call patterns.
• Keep names meaningful; reserve comments for non-obvious invariants.
• Treat dense special cases as evidence of a mistaken model.

Get the diff via attached context when present; otherwise git (status, diff, logs, merge-base). One clarifying prompt if comparison base unclear—never assume silently. Multiple roots: rinse per checkout; harp on duplication or drifting contracts.

Fan out narrow parallel explore-style probes when mental model/call graphs/conventions/outside hunks justify it—not one sprawling agent—and stay read-only unless the user commissioned edits.

Order