Claude Skill MartBrowse skillsQuick linesLearn by videoTerminal guideWhat is a Skill?
 
← Back to list

Project-Wide Audit

A fan-out audit pipeline that runs every analysis skill in parallel and produces a unified health dashboard in Markdown and HTML.

Dev & CodingAdvanced★ 403⑂ 32AI score 9/10Last updated: Sep 25, 2026

What it does

  • Confirms scope first (all files / specific paths / heuristically chosen high-risk areas), then partitions source files into at most 10 groups, excluding generated and vendored directories like node_modules/, dist/, and vendor/.
  • Checks .turbo/threat-model.md, reusing it only if its cited paths still resolve; otherwise it offers to create a fresh threat model.
  • Dispatches one agent per partition for /review-code (correctness, security, api-usage, consistency, simplicity) plus /peer-review, and project-wide agents for coverage, dependencies, tooling, agentic setup, and dead code — all in a single parallel batch.
  • Aggregates every finding, runs /evaluate-findings once to validate and deduplicate, then writes .turbo/audit.md with a Pass/Warn/Fail dashboard driven by P0/P1 severity thresholds.
  • Generates a self-contained .turbo/audit.html with a color-coded health grid, severity summary bar, sticky nav, collapsible sections, print styles, and responsive layout.
  • Analysis only: it never edits, stages, or commits code, and empirical checks run in a throwaway git worktree with strict process-group cleanup and verification.

Who it's for

  • Tech leads who need a one-page health snapshot before a release or handover
  • Engineers inheriting a legacy codebase who need a risk map fast
  • Solo developers who want security, coverage, and dependency checks in one pass
  • Existing turbo skill-set users who want their review skills orchestrated

Examples

  1. "Run a full audit of this project" → scope prompt, partitioned fan-out, then .turbo/audit.md and audit.html are written.
  2. "Audit src/auth and src/payments only" → skips the scope question and focuses security and correctness review on those paths.
  3. "Project health check before shipping" → any category with a P0 is marked Fail, giving you a concrete release gate.

· · · Install guide · · ·

Try it now, no install

Paste this into Claude to use the skill without installing anything.

Read the instructions in this file and follow them to help me:
https://raw.githubusercontent.com/tobihagemann/turbo/HEAD/claude/skills/audit/SKILL.md

What I want: (describe your task here)

If Claude can't open the link, open it yourself and paste the contents instead.

↓ If it works for you, download the ZIP below and install it. Then it runs on its own — no pasting each time.

Install in the Claude app (no terminal)
  1. Download the ZIP with the button below.
  2. In Claude, open Settings → Capabilities and turn on 'Code execution and file creation'. (one time)
  3. Go to Customize → Skills → + → 'Upload a skill' and upload the ZIP.
↓ Download ZIP
Install in Claude Code

Let Claude do it — paste this into Claude Code

Install the skill I found on Claude Skill Mart.
Copy the claude/skills/audit folder from the GitHub repo tobihagemann/turbo into my ~/.claude/skills/audit/.
When it's done, tell me in one line what this skill can do.

Install with a command instead

git clone https://github.com/tobihagemann/turbo.git /tmp/turbo && mkdir -p ~/.claude/skills && cp -r /tmp/turbo/claude/skills/* ~/.claude/skills/

⚠ This is a third-party skill. Check the source repository before installing.

  1. Open a terminal.
  2. Clone the repository: git clone https://github.com/tobihagemann/turbo.git /tmp/turbo
  3. Create the skills directory: mkdir -p ~/.claude/skills
  4. Copy the whole skill set, since this skill invokes /review-code, /peer-review, /evaluate-findings, /find-dead-code, and /frontend-design: cp -r /tmp/turbo/claude/skills/* ~/.claude/skills/
  5. Verify with ls ~/.claude/skills that audit and the sibling review skills are present.
  6. Restart Claude Code, open your project directory, and ask "audit the project".
  7. Reports land in .turbo/audit.md and .turbo/audit.html; add .turbo/ to your .gitignore.
  8. A full audit spawns many agents and can be slow and token-heavy — try a narrow path scope on your first run.
View source on GitHub ↗License: MIT