code-audit

Audits production source files against CQ1-CQ40 quality gates and CAP anti-patterns with tiered scoring.

6|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/greglas75/zuvo --skill code-audit-greglas75
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-audit
Source: https://github.com/greglas75/zuvo/tree/main/skills/code-audit
Command: npx skills add https://github.com/greglas75/zuvo --skill code-audit-greglas75

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It gives teams a systematic, evidence-backed way to measure production code quality across an entire codebase, replacing ad-hoc reviews with a consistent 40-gate checklist, anti-pattern catalog, and prioritized fix plan. ## Core Features & Use Cases - Batch quality triage: Scans all production files (or a scoped path, services, or controllers) and classifies each into Tier A/B/C/D based on CQ1-CQ40 gate scores and CAP1-CAP29 anti-patterns. - Tool-verified findings: Uses CodeSift tools (audit_scan, find_dead_code, find_clones, scan_secrets, empty-catch pattern search) to produce deterministic HIGH-confidence findings with file:line citations. - Stack-aware analysis: Activates framework-specific audits for TypeScript, Python, PHP, Kotlin, NestJS, Next.js, Astro, React, Django, FastAPI, Prisma, and more. - Use Case: Before a major release, run a full-project audit to flag hardcoded secrets, SQL injection risks, dead code, and duplication, then receive a prioritized execution plan ordered by risk. ## Quick Start Ask the AI to run a code audit on the whole project with "audit all production files and give me the tier report and prioritized fix plan".

Frequently Asked Questions about code-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a code quality audit on my entire project?

Invoke the audit with the 'all' argument to scan every production file, excluding tests, node_modules, and build output. Files are batched in groups of 6-10 and scored against the CQ1-CQ40 checklist, producing a tiered report with a prioritized fix plan.

What is the difference between --quick and --deep audit modes?

Quick mode runs binary pass/fail checks with batches of 10 files for fast triage, while deep mode collects per-gate evidence and fix recommendations for every file. Auditing a single file always forces deep mode with full evidence.

Which languages and frameworks does the code audit support?

It supports TypeScript, JavaScript, Python, PHP, and Kotlin, with dedicated stack-specific audits for NestJS, Next.js, Astro, React, Hono, Django, FastAPI, Flask, Yii, and Prisma. Generic CodeSift tools cover Express and Fastify.

What happens if CodeSift tools are unavailable during an audit?

The audit falls back to Grep, Read, and Glob for discovery and pattern matching, and notifies the user once. Dead-code and clone pre-scans are skipped in degraded mode, reducing automated detection coverage for CQ13 and CQ14.

What findings automatically trigger a Tier D classification?

Hardcoded secrets, SQL string concatenation with user input, eval() with dynamic input, unsanitized HTML reaching the DOM, unsafe pickle/yaml loading, and shell=True subprocess calls all trigger automatic Tier D. These red flags bypass the full checklist evaluation.

When should I use code-audit instead of a single-file code review?

Use code-audit for batch triage across many production files, such as pre-release health checks or codebase onboarding. For single-file review, refactoring, or test quality assessment, the documentation directs you to the dedicated review, refactor, and test-audit skills instead.