菜单
Hyperflow code review. Use when the user wants the current diff, a commit, branch, or PR reviewed — verbs like audit, review, "check for issues", "security check", "code review". Multi-level review (L1 quick → L5 exhaustive), writes findings to .hyperflow/audits/, then a fix-gate.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when applying Hyperflow's orchestration doctrine in Codex, Antigravity, Grok, OpenCode, or another portable surface. Auto-invoke for non-trivial engineering work: build, implement, add, refactor, debug, fix, review, audit, plan, design, brainstorm, ship, or deploy. Trigger with /hyperflow:hyperflow, "use hyperflow", "apply the doctrine", or automatically on any task-shaped message.
Use when a request needs shaping before any code is written — a rough or vague prompt to sharpen, an ambiguous idea to design, or a clear-enough task to decompose. One chain-starter that amplifies the prompt, designs the approach, and decomposes it into a batched task file, skipping whichever phases the request doesn't need, then STOPS at a build-location gate (build here, hand off to another session, or just keep the plan). Plan never implements. Trigger with /hyperflow:plan, "design this", "plan this", "decompose this", "how should we", "what's the best way to", "break this down", "enhance this prompt".
Use when ready to ship — runs pre-push gates (lint, typecheck, build, tests, security sweep), commits, releases, and pushes. Standalone, never auto-invoked. Push always requires explicit confirmation. Trigger with /hyperflow:deploy, "ship it", "ready to push", "release", "cut a release", "deploy".
Use when the user wants to archive completed hyperflow artefacts for a slug, clear ephemeral leftovers (usage ledgers, session log bloat, settled commit queues, terminal background buffers), and optimise durable memory — never source code. Also the phase contract lifecycle skills (dispatch/deploy/handoff) invoke at completion when cleanup.reapOnComplete is true. Trigger with /hyperflow:reap, hyperflow reap, "reap completed tasks", "archive finished slug", "clean up after dispatch", "post-completion cleanup".
Use when a task file exists in .hyperflow/tasks/ and workers need dispatching. Fans out parallel workers under per-batch Reviewers, runs a final integration review, and commits per sub-task. Endpoint of the auto-chain — no auto-deploy. Trigger with /hyperflow:dispatch, "run the plan", "execute the task", "build it", "run the batches".
Use when managing a two-session handoff — inspecting, picking up, or reviewing a committed handoff package produced by a session=two scope run. The operator interface over the cross-environment handoff lifecycle (plan in one session, build in another, review back in the first). Trigger with /hyperflow:handoff, "list handoffs", "pick up the handoff", "review the handoff build".
| name | hyperflow-audit |
| description | Hyperflow code review. Use when the user wants the current diff, a commit, branch, or PR reviewed — verbs like audit, review, "check for issues", "security check", "code review". Multi-level review (L1 quick → L5 exhaustive), writes findings to .hyperflow/audits/, then a fix-gate. |
Multi-level review over a target (default: git diff HEAD + staged). Follow the hyperflow doctrine. Security scan is mandatory at L3+.
| L | Checks |
|---|---|
| 1 | syntax, obvious bugs, formatting |
| 2 | L1 + spec compliance, naming, edge cases |
| 3 | L2 + cross-file consistency, integration risks, security (secrets, injection, path traversal, XSS, missing validation) |
| 4 | L3 + architecture, scalability, accessibility |
| 5 | L4 + adversarial probing, perf profiling, alternatives |
Default to L2; elevate to L3 when the diff touches auth, data, money, or external input.
[Critical] / [Important] / [Suggestion] / [Praise] with file:line + a concrete fix..hyperflow/audits/<YYYY-MM-DD-HHmm>-<scope>.md (status table → TL;DR → findings → security-scan table). Print a one-line summary pointing at the file.Fix all (Recommended) / Critical+Important / Critical only / No. On a fix choice, route the findings into hyperflow-plan → hyperflow-dispatch. On SECURITY_VIOLATION, skip the gate and surface immediately.Audit clean and still writes the file for history.