Audit Method
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.
Install
npx skills add wolverin0/claude-skills --skill audit-methodgit 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-method ~/.claude/skills/audit-methodPersonal 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 Method (Setup Phase) This skill produces the foundational understanding of the codebase that all subsequent domain audits depend on. It does NOT produce findings. It runs in three sub-phases: tool fingerprinting, repository inventory, system mapping. --- ## Required preflight: stack-completeness gate Before any domain audit runs, produce a stack-completeness inventory. This gate is required, not optional. The output must include concrete counts for: - X routes - Y DB migrations - Z Supabase tables - W env vars - V feature flags Write these counts to `inventory.json` in the audit run directory and include the source globs/commands used to produce each count. If a count cannot be produced, write `UNABLE` plus the exact blocker; do not omit the field. Every downstream domain audit findings section MUST include a completeness line tied to this inventory, such as `Checked N of X routes`, `Checked N of Y migrations`, `Checked N of Z Supabase tables`, `Checked N of W env vars`, or `Checked N of V feature flags` as relevant to that domain. Missing completeness lines mean the audit is incomplete and the orchestrator must not emit `[AUDIT COMPLETE]`. --- ## Phase 1 — Tool fingerprinting Goal: detect what stack the audited code actually uses, so subsequent audits don't apply foreign-ecosystem assumptions (R7). ### Detection commands
Details
- Skill name
audit-method- Repository
- wolverin0/claude-skills
- Path
skills/audit/audit-method/SKILL.md- Repo updated
- 17 November 2026
FAQ
What does the Audit Method skill do?
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.
How do I install the Audit Method skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add wolverin0/claude-skills --skill audit-method. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Audit Method 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.
Audit Orchestrator
41wolverin0/claude-skills
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).
Audit Domain 13 Code Integrity
41wolverin0/claude-skills
Audit code integrity and coherence — duplication, hallucinated references, Tambon signatures, spec drift, Frankenstein patterns, mystery code. THIS DOMAIN incorporates findings from the Tambon hunt and blind spots B9, B12, B13, B14. Run as part of /audit Phase E.
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.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.