audit

Overview

What is the audit Skill?

The audit skill is designed to help frontend developers and teams systematically assess the technical quality of their codebase. It runs comprehensive checks across five key areas: accessibility (A11y), performance, theming, responsive design, and detection of anti-patterns. After scanning, it generates a scored report (P0–P3 severity) with actionable recommendations, making it easier to prioritize and plan improvements.

Who Should Use audit?

This skill is ideal for frontend engineers, QA specialists, and product teams who want to:

• Ensure their code meets accessibility and performance standards
• Identify technical debt and anti-patterns
• Prepare for compliance reviews or technical audits
• Get actionable, prioritized feedback without manual code review

Problems audit Solves

• Detects common accessibility issues (contrast, ARIA, keyboard navigation, semantic HTML, alt text, form labeling)
• Flags performance bottlenecks and inefficient patterns
• Highlights theming and responsive design gaps
• Surfaces anti-patterns that can impact maintainability and user experience

How to Use

Installation Steps

1. Add the audit skill to your project:

   npx skills add https://github.com/pbakaus/impeccable --skill audit
   

2. Review the core documentation:

   • Start with SKILL.md for a full overview of audit's workflow and requirements.
   • Check README.md, AGENTS.md, and metadata.json for additional context.
   • Explore the rules/, resources/, references/, and scripts/ folders for supporting files and custom checks.

Preparation Before Running audit

• Invoke $frontend-design: This ensures design principles and anti-patterns are considered. Follow the Context Gathering Protocol as described in the documentation.
• If no design context exists: Run $teach-impeccable first to establish a baseline.

Running an Audit

• The audit skill performs a code-level scan, not a design critique. It checks only what is measurable and verifiable in your implementation.
• After running, you'll receive a detailed report with severity ratings (P0–P3) and a prioritized action plan. The skill documents issues but does not fix them automatically.

When to Use audit

• During code reviews or before major releases
• As part of CI/CD pipelines for ongoing quality assurance
• When preparing for accessibility or performance compliance checks

FAQ

What does the audit skill check for?

The audit skill checks for accessibility issues (like contrast, ARIA, keyboard navigation), performance bottlenecks, theming consistency, responsive design flaws, and code anti-patterns.

Does audit fix issues automatically?

No, audit identifies and documents issues, providing a scored report and actionable recommendations. Fixes should be applied manually or with other tools.

Is audit suitable for backend or non-frontend projects?

No, audit is focused on frontend codebases and is not intended for backend or purely server-side projects.

Where can I find more details about audit's checks?

Open the Files tab in the repository to explore SKILL.md and supporting folders for detailed criteria, scoring guidelines, and references.