| name | zl-code-review |
| description | Zhulong code review workflow focused on spec drift, code-map impact, behavioral risk, tests, and evidence. |
Zhulong Code Review
Use this when the user invokes /zl-code-review or asks for a Zhulong-grounded
review.
Treat the user text after /zl-code-review as the review scope.
Required Flow
-
From the repository root, run:
{{ZL_CLI}} workflow run code-review --target . "$ARGUMENTS"
-
Read the generated review packet and handoff.
-
Inspect the diff and affected source files directly.
-
Check whether behavior claims match the request, active records, source,
tests, or optional project documents when present.
-
Use the code map for impact and dependency checks:
{{ZL_CLI}} graph status --target .
{{ZL_CLI}} graph query --target . "<changed symbol or module>"
-
Lead with findings ordered by severity. Include file and line references.
-
Mention missing tests, missing evidence, stale graph data, or unresolved
specification ambiguity as review risks.
-
If the review creates durable verification evidence, record it with
{{ZL_CLI}} evidence record --target . ... --writeback <active-record>.
-
Follow core/workflows/code-review.md and perform the review inline with Zhulong
gates.
Keep the user-facing workflow name /zl-code-review. When suggesting next
commands to the user, suggest /zl-* commands, never /gsd-* commands.
