Check What the Review Command Actually Runs

Before building a review workflow, inspect the commands and plugins available in your installation. A command named /code-review may come from an installed plugin or a local skill; its name does not establish its implementation or availability everywhere.

Read its instructions, permissions and inputs. Does it review the intended diff and base revision? Does it get a separate context? Does it receive the writer's conclusions before forming its own?

Then give it a bounded requirement: identify defects that affect correctness or a stated acceptance criterion, with a reproducing input or code path. Inspect each finding before changing the implementation.

A bundled or shared workflow can save setup time. It still needs the same scrutiny as one you wrote: correct scope, a visible evidence trail and a human decision about which findings deserve action.