skill-audit

Define the audit scope and criteria first, then use Glob and Grep to discover all audit targets and build a checklist. Execute each checklist item systematically, document pass/fail results with evidence, and categorize findings by severity before proposing fixes.

A code audit systematically checks the whole codebase against explicit criteria to find broken or inconsistent patterns, while a code review evaluates specific changes for quality. Use this audit process for comprehensive checks and a dedicated code review skill for pull-request-style feedback.

No, security vulnerability scanning is explicitly out of scope and should be delegated to a dedicated security audit skill. This process covers functional, consistency, completeness, and quality checks only.

Skip it for single-file searches where Grep or Glob suffices, performance profiling, and security-specific scans. The full five-phase process is designed for broad, multi-area verification, not targeted lookups.

Findings are grouped into Critical (broken functionality), Major (degraded functionality), and Minor (inconsistencies). The remediation plan sequences fixes into phases with effort estimates, starting with critical issues.