jeremylongshore/tons-of-skills-marketplace / plugins/ai-agency/hyperflow/templates/antigravity/skills/hyperflow-audit
hyperflow-audit
VerifiedHyperflow 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
- 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.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |