Hyperflow audit
425 plugins, 2,810 skills, 200 agents for Claude Code. Open-source marketplace at tonsofskills.com with the ccpi CLI package manager.
npx -y skills add jeremylongshore/claude-code-plugins-plus-skills --skill hyperflow-auditAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its author says it does
Copied from the file, not written here
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.
SKILL.md
1.9 KB, as published. Nobody here has run it
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/<YYYY-MM-DD-HHmm>-<scope>.md(status table → TL;DR → findings → security-scan table). Print a one-line summary pointing at the file. - 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-plan→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.