mirror of
https://github.com/alibaba/higress.git
synced 2026-07-23 21:00:41 +08:00
d5f2b624fb
Signed-off-by: johnlanni <johnlanni@users.noreply.github.com> Co-authored-by: johnlanni <johnlanni@users.noreply.github.com> Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
1.1 KiB
1.1 KiB
name, description, category, tags
| name | description | category | tags | ||
|---|---|---|---|---|---|
| Issue Spec: Verify | Run final issue-spec verification across traceability, questions, review findings, PR rationale, PR checks, and durable spec draft. | Workflow |
|
Issue Spec Verify
Use when the user asks for /issue-spec:verify, issue-spec verify, or final readiness evidence before merge/archive.
Steps
-
Run focused project tests and record evidence in VERIFY comments.
-
Run issue-spec verify-links --repo higress-group/higress --proposal --design --implement --json.
-
Render a durable spec draft:
issue-spec archive durable-spec --repo higress-group/higress --proposal <issue> --capability <capability> --output /tmp/<capability>-spec.md --json -
Run final verify:
issue-spec verify --repo higress-group/higress --proposal <issue> --design <issue> --implement <issue> --pr <pr> --durable-spec /tmp/<capability>-spec.md --json -
Final verify must fail if blocking questions, missing links, missing PROCESS rationale, open P0/P1 findings, failed or pending PR checks, or durable spec omissions exist.