Remove acceptance from model discretion
Use when.
You
run
Claude
Code
2.1.215
or
later
and
your
interactive,
CI,
or
unattended
workflow
assumed
Claude
would
opportunistically
invoke
the
bundled
/verify
or
/code-review
skill
before
declaring
work
complete.
This
includes
prompts
such
as
“verify
before
done”
that
never
inspect
the
resulting
tool
trace.
Action.
Change
the
supervisor’s
completion
transition,
not
merely
its
prose.
After
the
final
edit,
submit
/verify
as
a
standalone
skill
call,
then
submit
/code-review high
with
an
explicit
target
such
as
main...feature.
Capture
both
invocations
and
their
outputs
in
the
run
record.
If
either
step
causes
another
edit,
invalidate
both
receipts
and
rerun
them
in
that
order.
Keep
deterministic
tests,
builds,
and
policy
checks
outside
these
model-operated
skills;
for
unattended
sessions,
enforce
those
checks
with
CI
or
a
blocking
Stop
hook.
/verify → explicit /code-review high <target> → inspect receipts → release or repair and restart the gate
Acceptance check.
Canary
the
upgraded
harness
on
a
disposable
change.
Pass
only
when
the
transcript
contains
explicit
post-edit
invocations
of
both
named
skills;
/verify
records
an
observed
running-app
result;
review
reports
no
unresolved
correctness
finding;
independent
checks
are
green;
and
no
write
occurs
afterward.
A
prose
assurance,
a
pre-edit
run,
or
a
missing
trace
fails
the
gate.
Caveat.
The
release
note
publishes
neither
rationale
nor
regression
output.
/verify
can
infer
the
wrong
launch
recipe
for
projects
with
databases,
environment
files,
GUIs,
or
multi-step
startup;
record
a
project
run
skill
or
use
an
external
oracle.
A
project
skill
can
also
shadow
a
bundled
name,
and
code-review
findings
do
not
themselves
approve
or
block
a
pull
request.