4 AI reviewers clean your code at the same time with /simplify

Four AI reviewers cleaning your messy code at the same time, from one command.

Run it

/simplify

What the four reviewers do

Each one has a different job on the code you changed:

1. Find code you could reuse instead of rewriting.
2. Simplify messy parts.
3. Make slow parts faster.
4. Check the change is at the right level of design.

Then it applies the fixes.

What it does not do

It does not hunt for bugs. For bugs, use /code-review. For security problems, use /security-review.

See exactly what changed

/diff

Read the diff before you commit. Cleanups can still change behaviour, so run your tests afterwards.

A good routine

1. Finish your change and get the tests passing first, so you start from a version you know works.
2. Commit, then run /simplify. If a cleanup goes wrong, that commit is your way back.
3. Read the result with /diff, one file at a time. Ask Claude why it made any change you do not understand.
4. Run the tests again. If one fails, undo that cleanup instead of patching around it.
5. Commit the cleanups on their own, apart from the feature, so a reviewer can read each part separately.

When to skip it

On a one-line fix there is little to tidy, and on code you are about to delete it is wasted effort. It earns its keep after a long session where the code grew in small steps and nobody stepped back to look at the whole change.

More quick tips

• Scan your code for security bugs before you push
• Save points for AI coding: branch your chat and undo
• All terminal tips and tricks