Audit Orchestrator
Conduct a full technical due diligence audit of a vibe-coded codebase. Use when the user types `/audit`, asks for a "full audit," asks for a "due diligence review," asks "is this codebase ready to ship?", or asks for a comprehensive code review of an entire repository (not a single PR). Coordinates the 13 domain skills, the hard-stop hunt, the Tambon LLM-signature hunt, and the blind-spot walk. Produces a single dual-layer report (founder view + technical evidence).
Install
npx skills add wolverin0/claude-skills --skill audit-orchestratorgit clone --depth 1 https://github.com/wolverin0/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/skills/audit/audit-orchestrator ~/.claude/skills/audit-orchestratorPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Skill: Audit Orchestrator You are the conductor of a multi-domain technical due diligence audit. Your job is sequencing, not finding. The actual hunting happens in specialized skills and subagents that you invoke and stitch together. This is a long-running, multi-phase task. Before doing anything, plan the run. --- ## What this skill produces A single report following the format in `~/.codex/context/audit-report-format.md`. Founder view + technical evidence, with severity census, verdict, and remediation plan at the top and 13 domain sections below. --- ## What this skill does NOT do - Find findings directly. The domain skills do that. - Modify any code. Read-only audit. - Produce AI fix prompts for every finding inline. The `audit-fix-generator` skill does that on demand. - Deliver a partial audit silently. If running out of context, emit a truncation marker per Rule R6. --- ## Pre-flight (do once, at the start) Before invoking any other skill, do this in order: ### 1. Load the rules Read `~/.codex/context/audit-rules.md` end-to-end. The seven rules (R1-R7) apply to the entire audit. ### 2. Load the report format Read `~/.codex/context/audit-report-format.md`. You're going to be producing this format; familiarize yourself. ### 3. Load the triage rubric Read `~/.codex/context/audit-triage-rubric.md`. The verdict at the top of the report is determined by the rules in this file. ### 4. Create inventory.json preflight
Details
- Skill name
audit-orchestrator- Repository
- wolverin0/claude-skills
- Path
skills/audit/audit-orchestrator/SKILL.md- Repo updated
- 17 November 2026
FAQ
What does the Audit Orchestrator skill do?
Conduct a full technical due diligence audit of a vibe-coded codebase. Use when the user types `/audit`, asks for a "full audit," asks for a "due diligence review," asks "is this codebase ready to ship?", or asks for a comprehensive code review of an entire repository (not a single PR). Coordinates the 13 domain skills, the hard-stop hunt, the Tambon LLM-signature hunt, and the blind-spot walk. Produces a single dual-layer report (founder view + technical evidence).
How do I install the Audit Orchestrator skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add wolverin0/claude-skills --skill audit-orchestrator. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Audit Orchestrator popular?
It lives in wolverin0/claude-skills, which has 41 GitHub stars and 1 forks.
Related skills
UI UX Pro Max
41wolverin0/claude-skills
UI/UX design intelligence for web and mobile. Includes 50+ styles, 161 color palettes, 57 font pairings, 161 product types, 99 UX guidelines, and 25 chart types across 10 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui, and HTML/CSS). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, and check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, and mobile app. Elements: button, modal, navbar, sidebar, card, table, form, and chart. Styles: glassmorphism,
Audit Blind Spots
41wolverin0/claude-skills
Walk the B1-B19 AI-to-AI blind-spot catalog systematically. Use during the audit pipeline AFTER hard-stops and Tambon hunt and BEFORE the 13 domain audits. Output: PRESENT / NOT PRESENT for each B-class with evidence. Findings flow into the appropriate domains.
Audit Decisions
41wolverin0/claude-skills
Standardize remediation decisions, baseline-policy entries, and legal-review banners for accepted, deferred, or policy-blocked audit findings.
Build CLI Plugin
45pjt222/agent-almanac
Build a plugin or adapter for a CLI tool using the abstract base class pattern. Covers defining the contract (static fields, required methods), choosing an installation strategy (symlink, copy, append-to-file), implementing detection, install/uninstall with idempotency, listing, auditing, and registering the plugin. Use when adding support for a new framework to a CLI installer, building a plugin system for any multi-target tool, or extending an existing adapter architecture.
Audit Method
41wolverin0/claude-skills
Run the methodology setup phase of a technical audit — fingerprint the stack, inventory the repository, and produce a system map. Use this BEFORE running any audit domains. Output: detected stack, repo summary, and high-level architecture in 3-5 paragraphs. No findings yet.
Catalog Collection
45pjt222/agent-almanac
Catalog and classify materials using standard library systems. Covers descriptive cataloging, subject headings, call number assignment using Dewey Decimal and Library of Congress Classification, MARC record basics, shelf organization, and authority control for consistent access points. Use when organizing a personal, institutional, or community library from scratch, assigning call numbers and subject headings to new acquisitions, reclassifying a collection that has outgrown its original system, or establishing authority control for authors, series, or subjects.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.