simplify

Run the Skill against your git diff; it launches three parallel review agents covering reuse, quality, and efficiency, then fixes each finding directly. If there are no git changes, it reviews files you mentioned or edited in the conversation.

The review checks three dimensions: reuse (duplicated utilities and inline logic an existing helper covers), quality (redundant state, parameter sprawl, copy-paste, stringly-typed code), and efficiency (redundant computation, N+1 patterns, leaks, sequential independent operations).

Avoid simplifying when it means inlining a named helper, merging unrelated logic, removing load-bearing indirection or error handling, trading readability for line count, or touching code outside the diff. Code you do not fully understand should go back to the understanding phase first.

No. The verification phase requires existing tests to pass unmodified; tests needing changes signal that behavior changed and the simplification must be revisited. Error handling must never be removed or weakened.

Use simplify for diff-level cleanup of reuse, quality, and efficiency within changed code. For module-level structural work such as seams, ports, and depth, use the improve-architecture skill instead, as simplification stays scoped to the diff.