Claude Code shipped two new commands with version 2.1.63 on February 28th: /simplify and /batch. They sound modest. They’re not.
/simplify – the code reviewer that never gets tired
You’ve built a feature, it works, the tests pass. But you know there’s room for improvement. That’s exactly where /simplify comes in.
The command looks at your recent git changes and systematically checks what could be better. Duplicated logic, missed abstractions, performance issues – everything a good code reviewer would flag. Except this reviewer never has a bad day.
In practice, that means: you build your feature, don’t commit yet, and run /simplify over it. The results are often surprisingly good – especially with larger changes where you’ve lost the big picture.
/batch – when you need to touch hundreds of files
Every developer knows the pain: framework migration, API overhaul, or just a rename that ripples through half the project. /batch was built exactly for this.
You describe what needs to change, and /batch works through your entire repository. File by file, consistent, without losing focus after the 50th modification.
It works in any git repository and handles complex transformations too – not just simple find-and-replace operations.
What else is in 2.1.63
Beyond the two new commands, there are a few more improvements that help in daily work:
Project configs and auto-memory are now shared across git worktrees. So if you’re working in multiple branches of the same repo, you’ll have the same settings everywhere. Hooks also now support HTTP POST requests with JSON – letting you integrate external services directly without the detour through shell scripts.
My take
These two commands close a gap that Claude Code has had. Editing individual files was already solid – but large refactorings or migrations were tedious. /batch fundamentally changes that. And /simplify will probably become a permanent part of every feature branch for me.
Update with claude update – it’s worth it.
Sources: