name	simplify
description	Reduce a change to the minimum that solves the problem. Use when code is over-engineered or a diff is bloated.
when_to_use	over-abstraction, a 200-line diff for a small ask, premature generality

Simplify

Over-engineering is the default failure mode. Cut it:

Premature abstraction — a class/strategy/factory for one caller. Inline it. Abstract on the THIRD use, not the first.
Speculative config — a parameter/flag/env var for something that never changes. Hardcode it until there's a real reason.
Dead flexibility — an interface with one implementation, a generic with one type. Delete the indirection.
Defensive noise — null checks on values that can't be null, try/except for errors that can't happen. Handle only real failure modes. Test: can you justify every changed line by a direct connection to what was asked? If a line is there "while I was in there", revert it.

Más de este repositorio

mismo repositorio

adversarial-verify

YaoYinYing/REvoDesign

Review a diff against the goal spec assuming the code is BROKEN. The reviewer that lives in the maker's head always agrees with itself — this pulls review into a hostile, separate pass. Invoke after every code change before marking work done.

2026-07-122

authz-check

YaoYinYing/REvoDesign

Verify that an endpoint checks ownership, not just authentication. Use on any handler that reads or mutates user data.

2026-07-122

bisect-regression

YaoYinYing/REvoDesign

Find the exact commit that introduced a bug. Use when something worked before and broke, and you don't know which change did it.

2026-07-122

changelog-from-diff

YaoYinYing/REvoDesign

Turn a set of commits or a diff into a clean, user-facing changelog entry. Use before a release or PR description.

2026-07-122

clean-commits

YaoYinYing/REvoDesign

Turn messy WIP into clean, atomic commits with messages that explain why. Use before opening a PR.

2026-07-122

context-budget

YaoYinYing/REvoDesign

Keep the agent's context lean so accuracy doesn't collapse. Use on long sessions, big files, or when the agent starts hallucinating.

2026-07-122

name	simplify
description	Reduce a change to the minimum that solves the problem. Use when code is over-engineered or a diff is bloated.
when_to_use	over-abstraction, a 200-line diff for a small ask, premature generality

Simplify

Over-engineering is the default failure mode. Cut it:

Premature abstraction — a class/strategy/factory for one caller. Inline it. Abstract on the THIRD use, not the first.
Speculative config — a parameter/flag/env var for something that never changes. Hardcode it until there's a real reason.
Dead flexibility — an interface with one implementation, a generic with one type. Delete the indirection.
Defensive noise — null checks on values that can't be null, try/except for errors that can't happen. Handle only real failure modes. Test: can you justify every changed line by a direct connection to what was asked? If a line is there "while I was in there", revert it.