hyperflow-audit
/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.
- Author
- jeremylongshore ↗
- Repository
- tons-of-skills-marketplace ↗
- Licence
- MIT
- Last repository change
- 26.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
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.
Triggers from the description
Original author 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.
How it works
- Levels
- Steps
- Rules
SKILL.md preview
--- 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. --- # 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 1. **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.
Versions
The database has no other skills named hyperflow-audit.
Database snapshot: 13.11.2026 · package version 440b185060ef (SHA-256 digest of the entire package)
Downloads in the last 30 days: 3 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100audit
Use when the user wants a code review on recent changes — quality, spec, security, or performance feedback. Triggers a multi-level (L1-L5) review with a standalone Reviewer; on NEEDS_FIX, offers to apply findings via /hyperflow:plan. Trigger with /hyperflow:audit, "review this… - 90hyperflow-scaffold
Hyperflow project setup. Use when starting hyperflow in a new project or refreshing its cache — "init hyperflow", "set up hyperflow", "refresh hyperflow", "scaffold hyperflow". One-shot setup of the .hyperflow/ project cache + memory and the .agent/workflows/hyperflow* slash… - 95scaffold
Use when starting hyperflow in a new project, re-initializing analysis, refreshing `.hyperflow/` cache, or installing multi-tool auto-detection shims (AGENTS.md, Cursor rules, GEMINI.md, CLAUDE.md). Trigger phrases — "init hyperflow", "set up hyperflow", "refresh hyperflow",… - 100scope
Use when the user says "plan this", "decompose this task", "break this down", or wants the task file before any code changes. Writes `.hyperflow/tasks/<slug>.md` with batched sub-tasks, then **auto-chains into `/hyperflow:dispatch`** — no manual gate. - 90code-review
Review changes since a commit, branch, or tag against the coding standards and the Spec. Use when the user wants a branch, a PR, or work in progress reviewed. - 90independent-review
Perform an independent, read-only review of a commit, branch, pull request, or code path and report reproducible findings. Use for review/audit requests; never silently remediate the target.