一键导入
x4-verify
Run X4 verification workflow. Use with /x4:verify to execute static verification, test implementation sync, test execution, and final report.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Run X4 verification workflow. Use with /x4:verify to execute static verification, test implementation sync, test execution, and final report.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | x4-verify |
| description | Run X4 verification workflow. Use with /x4:verify to execute static verification, test implementation sync, test execution, and final report. |
This skill owns /x4:verify sequencing.
Change name input (if provided) supports abbreviation token and must be resolved by x4-user-workflow "Change Name Resolution" rules.
change-name using x4-user-workflow rules before any action.Resolved change: <change-name>.openspec-verify-change.x4-test-impl.x4-test orchestration.x4:test-run.test_tasks.md (Chapter 4) via:
python3 skill-scripts/verify_bug_sync.py <change-name> --json
bugs.md is informational and does not drive gate decisionsx4-test-impl or x4-test stages.x4:test-run for bug-fix verification execution/result-apply.test_tasks.md Chapter 4 is the source of truth for bug closure gate./x4:verify must return a structured gate result for downstream /x4:archive:
verify_status: pass|fail
bug_gate: pass|fail
non_verified_bug_ids:
- BUG-xxx
bug_gate_summary: string
Rules:
bug_gate=pass only when verify_bug_sync.py returns no issues.bug_gate=fail when verify_bug_sync.py reports any issue.non_verified_bug_ids must list all blocking bug IDs/cases reported by verify_bug_sync.py when bug_gate=fail.test_tasks.md Chapter 4 + verify_bug_sync.py outputverify_status, bug_gate, non_verified_bug_ids, bug_gate_summary)Use when x4-e2e-test-doc-details needs fixture patch rules or helper guidance for X4 E2E test data.
Use when refining X4 `e2e_tests.md` into detailed E2E task, fixture, and implementation knowledge documents before Playwright implementation.
Use when creating or updating only the high-level X4 E2E test plan `e2e_tests.md` before detail expansion.
Review X4 E2E test documentation draft and gate x4-e2e-test-doc completion. Must run in a dedicated isolated subagent. Trigger with /x4:e2e-test-doc-viewer <change-name>.
Implement Playwright E2E tests for X4 changes from `e2e_test_tasks.md` and validate task-to-test mapping. Trigger with /x4:e2e-test-impl <change-name>.
Run change-scoped X4 Playwright E2E tests and validate implementation coverage against `e2e_test_tasks.md`. Trigger with /x4:e2e-test-run <change-name>.