Claude Code 2.1.215: /verify and /code-review No Longer Run on Their Own

Claude Code 2.1.215 shipped today with a single change on the menu. It looks small on paper, but it directly affects a habit a lot of people had picked up without noticing.

What changes

Until now, Claude Code could decide on its own to run the /verify or /code-review skills after modifying code, without you asking for it. It was a quiet safety net: you’d commit, and there was a chance Claude would run a verification or review pass before considering the work done.

That autonomous behavior goes away in 2.1.215. Both skills now only fire on explicit invocation: /verify or /code-review, typed by you.

Why it matters

If you never knew this auto-trigger existed, you’re not losing anything visible, just a safety net you didn’t know was there. But if your workflow leaned on it, even unknowingly, the gap will show up at the first unverified commit that ships without a review pass.

The change fits a broader pattern in recent releases: Claude Code is dialing back unrequested autonomous initiative (see also the subagent and web search caps added in 2.1.212) to make behavior more predictable and less surprising in unattended use.

What to do about it

Take the habit back explicitly:

• Run /verify before committing a nontrivial change, especially one touching production code.
• Run /code-review on your diff before pushing, if you want an automated second pair of eyes.
• If you want systematic coverage instead of a manual habit, a PostToolUse hook fired after Edit or Write can call these skills for you.

Should you update

Yes, no particular urgency: this isn’t a security fix, just a change to default behavior. The real risk is finding out about 2.1.215 in production, wondering why the automatic review you thought you had never ran.

Source: official Claude Code changelog.