| name | zl-verify-work |
| description | Zhulong verification workflow that ties tests, spec evidence, code-map checks, risks, rollback notes, and writeback together. |
Zhulong Verify Work
Use this when the user invokes /zl-verify-work or asks Zhulong to verify a
change.
Treat the user text after /zl-verify-work as the verification request.
Required Flow
-
From the repository root, run:
{{ZL_CLI}} workflow run verify-work --target . "$ARGUMENTS"
-
Read the generated verify packet and handoff.
-
Confirm the implemented files, relevant requirements, and active planning
records.
-
Run focused verification commands. Include tests, build, lint, typecheck, API,
or manual checks as appropriate.
-
Check code-map freshness and diff when structural or dependency impact matters:
{{ZL_CLI}} graph status --target .
{{ZL_CLI}} graph diff --target . --details
-
Record evidence, unresolved risks, rollback notes, and follow-ups:
{{ZL_CLI}} evidence record --target . "<summary>" --command "<command>" --result "<result>" --writeback <active-record>
-
Follow core/workflows/verify-work.md and verify inline with Zhulong gates.
Keep the user-facing workflow name /zl-verify-work. When suggesting next
commands to the user, suggest /zl-* commands, never /gsd-* commands.
