hyperflow-audit
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.
Allowed Tools
No tools specified
Provided by Plugin
hyperflow
Fifteen specialized slash commands turn one Claude session into a structured multi-agent engineering pipeline. Thinking models orchestrate, triage, and review; worker models execute in parallel — every step is a Worker → Reviewer pair, and every non-trivial phase fans into sub-phases with their own reviewers. Auto-routing is on by default — say 'audit the diff', 'debug this test', 'large migration', or 'run a workflow' and the orchestrator routes to the right skill without the /hyperflow:* prefix. /hyperflow:workflow uses Claude Code dynamic workflows for big tasks and a portable Codex/OpenCode adapter where native workflows are unavailable; /hyperflow:spec asks the questions a senior engineer would; /hyperflow:scope decomposes into a batched task graph; /hyperflow:dispatch fans out persona-stitched workers under tiered review; /hyperflow:amplify rewrites a rough prompt into a high-quality one before you run it. 15 composable personas, 6 adaptive flow profiles, and persistent project memory compound across sessions. Works across Codex App/CLI, Claude Code, OpenCode, and Antigravity.
Installation
This skill is included in the hyperflow plugin:
/plugin install hyperflow@claude-code-plugins-plusClick to copy
Instructions
hyperflow-audit — review phase (Antigravity single-agent)
Multi-level review over a target (default: git diff HEAD + staged). Follow the hyperflow doctrine. Security scan is mandatory at L3+.
Levels
| 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.
Steps
- Resolve scope (target arg or current diff). Read the changed files + their immediate dependencies.
- Review at the chosen level. Grade each finding
[Critical] / [Important] / [Suggestion] / [Praise]withfile:line+ a concrete fix. - Write the full report to
.hyperflow/audits/(status table → TL;DR → findings → security-scan table). Print a one-line summary pointing at the file.- .md - Fix gate via AskUserQuestion (only when Critical/Important exist):
Fix all (Recommended) / Critical+Important / Critical only / No. On a fix choice, route the findings intohyperflow-scope→hyperflow-dispatch. OnSECURITY_VIOLATION, skip the gate and surface immediately.
Rules
- Findings live in the file, not chat — chat shows only the summary box.
- A clean run (no Critical/Important) prints
Audit cleanand still writes the file for history.