Menu
Use for /he:verify; verification loop with tests, risk review, thermo review, E2E artifacts.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Use for /he:plan; stage 1 readiness with Treehouse, Grill Me, owner, proof path, PASS/FAIL.
Use for UI components, design systems, atomic design, tokens, themes, hardcoded visuals, or missing design SSOT.
Use for module boundaries, public APIs, ownership, abstractions, wrappers, test seams, or architecture review.
Use for visual PDFs: create, polish, export, verify decks, reports, proposals, one-pagers, or HTML-to-PDF.
Use for hard bugs, failing behavior, flaky tests, exceptions, regressions, or unexplained slowness before fixing.
Use for real UI E2E smoke/regression proof across web, Flutter, browser, Chrome, or device flows, with artifacts.
| name | he-verify |
| description | Use for /he:verify; verification loop with tests, risk review, thermo review, E2E artifacts. |
Stage 3/5. Use /he:verify after implementation or review fixes. Finish proof; do not timebox it.
Read ../workflow-help/references/route-map.md, ../test-quality/SKILL.md, and ../e2e/SKILL.md before acting.
he-state.json before/after each proof step; record proof findings in findings[]; validate it before any ready-yes handofftest-quality for assertion, fixture, or gap designguardrails[]; missing or failing guardrails route back to he-implementnode "$HOME/.agents/scripts/check-project-quality-gates.mjs" --require-push-gate . for React/Next, JS/TS, or Flutter work before readying shiphe-implement, update state, rerun affected proof only, repeat until clean or blockedNext: ready for /he:ship: yes/no. No transcript dump; next stage can start a fresh thread from state