Skill2.4k repo starsupdated today

hyperflow-audit

hyperflow-audit performs multi-level code review on git diffs, commits, branches, or pull requests, automatically escalating from quick syntax checks (L1) to exhaustive security and architecture analysis (L5) depending on what changed. It writes detailed findings to timestamped markdown files in .hyperflow/audits/, grades issues by severity, and offers a fix gate to route critical problems to remediation workflows.

View source Repository: claude-code-plugins-plus-skills

Install in Claude Code

Copy

git clone --depth 1 https://github.com/jeremylongshore/claude-code-plugins-plus-skills /tmp/hyperflow-audit && cp -r /tmp/hyperflow-audit/plugins/ai-agency/hyperflow/templates/antigravity/skills/hyperflow-audit ~/.claude/skills/hyperflow-audit

Then start a new Claude Code session; the skill loads automatically.

Definition

SKILL.md

# 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-scope` → `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.