Simplify Code
Make a change as plain as the problem allows, so that another engineer can read it quickly and trust it. Behavior stays identical. Fewer lines is a side effect, never the goal; clarity beats brevity.
Read references/operating-rules.md and references/code-quality.md first.
Use when
- A change is implemented and its checks pass
- The diff shows complexity signals: new wrappers or layers, single-use helpers or interfaces, options nobody passes, defensive checks for impossible states, duplicated logic, deep nesting, or comments that narrate
Skip it when the diff is small and already plain.
Inputs
- Scope: the change against a base commit (default: the uncommitted change plus the current branch's commits). Never the whole repository unless the user asks.
- Checks: the commands that cover the changed code, from
verify-workor the project. Without passing checks, there is nothing to preserve behavior against; get them first.
Procedure
- Read the whole change with its surrounding code and the project's patterns. Simplification means fitting the codebase, not a personal style.
- List the candidates. For each, name the signal from
references/code-quality.mdand the simpler form. Drop any candidate that would change behavior, a public interface, or code outside the scope. - Apply one at a time. After each, rerun the checks that cover it. If any fails, revert that simplification, and do not retry it.
- Stop when no candidate remains that makes the code clearer. Do not cycle on taste.
Typical simplifications:
- Inline a wrapper or single-use helper that only moves code around
- Remove an interface, factory, or option with one implementation or caller
- Delete validation that earlier validation or the types already guarantee
- Replace nested conditionals with guard clauses
- Reuse an existing helper instead of a new duplicate
- Remove dead code, unused exports, debug output, and narrating comments
Output
Simplified Inlined formatRefundPayload (one caller); removed RefundOptions (no caller passed options);
dropped a null check already guaranteed by the schema (refund-service.ts:31)
Kept RefundError subclass: matches the project's error-handling convention
Checks ✓ npm test -- refunds (23 passed) ✓ npm run typecheck rerun after the last editEscalate
- The clearest form needs a behavior or interface change: report it as a suggestion, and do not apply it
- The simplification would reach code outside the scope: report it, and do not apply it
Hand off
Return the simplified change, and the checks rerun, to the caller: hungry-jack, or the user. If the simplification touched code covered by browser or integration checks, say which ones should be rerun.
Before you finish, check your list of available skills for each skill named in this section. If any is missing, end your report with the missing names, this command, and the question "Should I install them for you, or will you install them yourself?" Follow "Missing companion skills" in references/operating-rules.md for the rest.
npx skills add akdevsaha-dev/factory-skills --skill hungry-jack plan-change implement-feature verify-work simplify-code review-changes reflectDone when
Every applied simplification has passing checks rerun after it, no behavior or interface changed, and nothing outside the scope was touched.