audit

Audit code files against project standards using parallel subagents.

1|Updated Dec 12, 2025

Search Tags:#automation #quality assurance #code review #linting #code audit #standards enforcement

Ready to run

npx skills add https://github.com/mjmiller3416/recipe-app --skill audit-mjmiller3416

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: audit
Source: https://github.com/mjmiller3416/recipe-app/tree/main/.claude/skills/audit
Command: npx skills add https://github.com/mjmiller3416/recipe-app --skill audit-mjmiller3416

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of auditing code files against project standards, ensuring consistency and quality across your codebase without manual intervention.

Core Features & Use Cases

Parallel Auditing: Audits multiple files simultaneously using isolated subagents for efficiency.
Configurable Standards: Leverages defined criteria files (.md) for various code types (components, pages, services, structure).
Tiered Audits: Performs full or lightweight audits based on the scope of changes.
Use Case: Before committing staged changes, run /audit staged to automatically check all modified files against project coding standards, accessibility guidelines, and architectural rules.

Quick Start

Run /audit staged to audit all currently staged files.

Frequently Asked Questions about audit

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

FAQPage Schema

How do I automate code quality audits for staged files before committing?▼

Automated code audits for staged files run parallel subagents to check modified code against configurable project standards. You initiate a staged file audit to automatically validate code quality and enforce architectural rules before committing.

How does parallel auditing work for large codebase structure checks?▼

Parallel auditing works by deploying isolated subagents that evaluate multiple files simultaneously against defined criteria files. This allows the system to perform tiered analysis based on change volume, enabling efficient full or lightweight directory scans across large project structures.

Can I enforce custom project coding standards for components and services?▼

You can enforce custom project coding standards by defining configurable criteria files in markdown for various code types. These files allow you to specify and automatically enforce architectural rules and quality benchmarks for components, pages, and services.

What is tiered analysis when auditing code changes?▼

Tiered analysis is an audit mechanism that adjusts review depth based on the volume of code changes. It performs full audits for large modifications and lightweight audits for smaller scopes, ensuring efficient standards enforcement without unnecessary processing overhead.

Do I need to define criteria files before running a directory scan?▼

You need to define criteria files before running a directory scan, as these markdown files provide the specific standards for components, pages, services, and overall structure. The automated audit uses these configurable criteria to evaluate your project files.