audit
/audit
Use when the user asks for a code review, "review this change", "review my PR", "review the diff", or wants quality/spec/security/perf feedback on recent changes. Triggers a multi-level review with a thinking-tier reviewer agent. Standalone — does not auto-chain.
- Author
- ccplugins ↗
- Repository
- awesome-claude-code-plugins ↗
- Licence
- Apache-2.0
- Last repository change
- 12.08.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 12.08.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Use when the user asks for a code review, "review this change", "review my PR", "review the diff", or wants quality/spec/security/perf feedback on recent changes. Triggers a multi-level review with a thinking-tier reviewer agent. Standalone — does not auto-chain.
Triggers from the description
Original author description
Use when the user asks for a code review, "review this change", "review my PR", "review the diff", or wants quality/spec/security/perf feedback on recent changes. Triggers a multi-level review with a thinking-tier reviewer agent. Standalone — does not auto-chain.
How it works
- Inputs
- Review Levels
- Flow
- Output Format
- Hand-off (no auto-chain)
- Doctrine
SKILL.md preview
--- name: audit description: Use when the user asks for a code review, "review this change", "review my PR", "review the diff", or wants quality/spec/security/perf feedback on recent changes. Triggers a multi-level review with a thinking-tier reviewer agent. Standalone — does not auto-chain. --- # Audit Standalone multi-level code review. Dispatcher — Opus 4.7 (thinking-tier). Workers — Sonnet 4.6. ## Inputs - **Target** — file path, line range, commit SHA, branch, or PR number provided by the user - **Default (no target)** — `git diff HEAD` + `git diff --staged` - **Level flag** — `--level 1` through `--level 5` (default — L2) ## Review Levels Adapted from [review-levels.md](../hyperflow/review-levels.md): | L | Name | Checks | |---|------|--------| | 1 | Quick | Syntax, obvious bugs, formatting | | 2 | Standard | L1 + spec compliance, naming, edge cases | | 3 | Thorough | L2 + cross-file consistency, integration risks, security | | 4 | Deep | L3 + architecture, scalability, accessibility | | 5 | Exhaustive | L4 + adversarial probing, perf profiling, alternatives | Security scan (hardcoded secrets, injection, path traversal, XSS, missing validation) is mandatory at L3+. See [security.md](../hyperflow/security.md). ## Flow 1. Resolve scope — use provided target or run `git diff HEAD` + `git diff --staged`. 2. Dispatch `Searcher — gathering context for review` (Sonnet 4.6) to map referenced files and load relevant project context. 3. Dispatch `**Reviewer** — reviewing <scope> at level L<n>` — Opus 4.7 (thinking-tier, non-negotiable). 4. Reviewer uses [reviewer-prompt.md](../hyperflow/reviewer-prompt.md) template with the diff, level definition, and any applicable spec. 5. Aggregate findings into structured output (see below). 6. Append durable patterns/gotchas to `.hyperflow/memory/learnings.md` per [memory-system.md](../hyperflow/memory-system.md). If any security issue found → emit `SECURITY_VIOLATION:` halt marker immediately. ## Output Format ``` ── Review Result ────────────────────── Scope: <files / range / commit> Level: L<n> Verdict: PASS | NEEDS_FIX | SECURITY_VIOLATION [Critical] - file:line — issue + required fix [Important] - file:line — issue + recommended fix [Suggestions] - file:line — optional improvement [Praise] - file:line — what's done well ─────────────────────────────────────── Agents: 1 searcher (sonnet) · 1 reviewer (opus) ``` ## Hand-off (no auto-chain) - **PASS** — suggest `/hyperflow:deploy` if the user is ready to release. Do not auto-ship. - **NEEDS_FIX** — print the finding list and suggest `/hyperflow:trace` (for root-cause bugs) or manual edits. Do not auto-fix. - **SECURITY_VIOLATION** — halt; do not transition. User decides remediation path. ## Doctrine Full rules in [DOCTRINE.md](../hyperflow/DOCTRINE.md). Output style in [output-style.md](../hyperflow/output-style.md).
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · ccplugins/awesome-claude-code-plugins | 100 | Apache-2.0 |
| marcel-bich/marcel-bich-claude-marketplace | 100 | MIT |
| jeremylongshore/tons-of-skills-marketplace | 100 | MIT |
| friendlyinternet/nuxt-crouton | 100 | MIT |
| userKael/rastro | 100 | MIT |
| Archont561/qgis-agent-harness | 100 | MIT |
| lilly-logic-labs/lll-skills | 100 | MIT |
| Come-In-Labs/agent-skills | 100 | MIT |
| minanyang/10x-agent | 100 | MIT |
Database snapshot: 13.11.2026 · package version 957bb40f7ab3 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100review
This skill should be used when the user asks to 'review changes', 'review my code', 'run a code review', 'review last commit', 'review recent changes', or 'check code against spec'. - 100go-code-review
WHEN: User wants an automated first-pass code review on a PR, diff, or set of changes. Also when asked "review this PR", "review my changes", or "what do you think of this code?" WHEN NOT: Full project audits (use go-code-audit), or when user just wants linting (use go-lint-audit). - 100ql-review
Part of the quantum-loop autonomous development pipeline (brainstorm \u2192 spec \u2192 plan \u2192 execute \u2192 review \u2192 verify). Two-stage code review. Spec compliance first, then code quality. Use after implementation or before merge. Triggers on: review code, code… - 100code-review
Three-stage code review protocol covering spec compliance, code quality, and domain integrity. Use this skill whenever the user asks to review code, prepare or check a PR, assess implementation quality, verify code against a spec or acceptance criteria, or audit for security and… - 100review
Review code quality, security, and maintainability before committing. Use when reviewing code changes, checking code quality, performing security review, or validating changes before commit. - 100code-review
Use to review code changes with a two-stage process - first checking spec/requirements compliance, then code quality. Works on staged changes, branches, or PRs.