How do I install the Hyperflow Audit skill?

Run npx skillmds@latest add jeremylongshore/hyperflow-audit in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Hyperflow Audit safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Hyperflow Audit?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Hyperflow Audit free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Hyperflow Audit?

jeremylongshore (@jeremylongshore) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Hyperflow Audit by jeremylongshore — Agent Skill

Name: Hyperflow Audit
Rating: 4.2 (5 reviews)
Author: jeremylongshore

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.

File contents

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] with file: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 into hyperflow-plan → hyperflow-dispatch. On SECURITY_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 clean and still writes the file for history.

Source: jeremylongshore/claude-code-plugins-plus-skills → plugins/ai-agency/hyperflow/templates/antigravity/skills/hyperflow-audit/SKILL.md

---name: hyperflow-auditdescription: 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.---# 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.## Steps1. **Resolve scope** (target arg or current diff). Read the changed files + their immediate dependencies.2. **Review** at the chosen level. Grade each finding `[Critical] / [Important] / [Suggestion] / [Praise]` with `file:line` + a concrete fix.3. **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.4. **Fix gate** via AskUserQuestion (only when Critical/Important exist): `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.## Rules- Findings live in the file, not chat — chat shows only the summary box.- A clean run (no Critical/Important) prints `Audit clean` and still writes the file for history.---**Source:** [`jeremylongshore/claude-code-plugins-plus-skills`](https://github.com/jeremylongshore/claude-code-plugins-plus-skills) → `plugins/ai-agency/hyperflow/templates/antigravity/skills/hyperflow-audit/SKILL.md`

Frequently asked questions