Command reference ยท Claude Code
/verify
Starts the project app and verifies that a change works end-to-end.
The /verify command is a bundled skill that confirms a code change by actually building, starting, and observing the project โ instead of relying only on tests or type checks. It's part of a trio of related skills: /run starts and operates the app to see a change in action, /verify specifically confirms that a change works as expected, and /run-skill-generator saves a project-specific startup recipe once under .claude/skills/run-<name>/ when the build or start process can't be detected automatically, for example due to a database, env file, or multi-stage build. As of v2.1.215, /verify only runs on explicit invocation; before that, Claude could also trigger it on its own. Without a saved recipe, /verify infers the start process from the project type, README, package.json, or Makefile, which works reliably for standard setups but can become inaccurate for more complex workflows. Requires Claude Code v2.1.145 or newer.
โ WHEN TO USE IT?
Observing the actual behavior before committing a non-trivial change
After a bugfix to the login flow, call /verify to run through the flow in the live app
Saving a fixed startup recipe after repeatedly unreliable automatic detection
Run /run-skill-generator once per project, then call /verify again
โ WHEN NOT TO?
Diff only affects tests, documentation, or configuration without runtime behavior
In that case there's no running interface or observable behavior to check
Better: Run the regular test suite instead; /verify isn't needed here
Project only runs with a database, credentials, or a multi-stage build that /verify doesn't know about
Without a saved recipe, /verify guesses the start process from README or package.json, which can fail for more complex setups
Better: Run /run-skill-generator beforehand so the startup recipe is permanently saved
SOURCES
- Claude Code docs (official) โ code.claude.com
MORE COMMANDS ยท Claude Code