audit

Audit code against Definition of Done and project patterns with test suite execution.

2|Updated Mar 1, 2026
One-click install
npx skills add https://github.com/pe-menezes/vibeflow-claude --skill audit-pe-menezes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit
Source: https://github.com/pe-menezes/vibeflow-claude/tree/main/skills/audit
Command: npx skills add https://github.com/pe-menezes/vibeflow-claude --skill audit-pe-menezes

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill ensures that code changes meet the project's quality standards by verifying against its Definition of Done and established patterns, preventing regressions and maintaining codebase integrity.

Core Features & Use Cases

  • Automated Quality Checks: Audits code against specific requirements in a spec file.
  • Test Suite Execution: Runs the project's test suite to catch functional errors.
  • Pattern Compliance: Verifies adherence to project-specific coding patterns and conventions.
  • Use Case: After implementing a new feature, use this Skill to automatically confirm that all Definition of Done items are met, tests pass, and the code follows the project's established design patterns before merging.

Quick Start

Audit the implementation for the feature described in the login-flow spec file.

Frequently Asked Questions about audit

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

FAQPage Schema
How do I verify code compliance against a Definition of Done before merging?

Code compliance against a Definition of Done is verified by auditing the implementation against a specified spec file and executing the project's test suite. This process identifies pattern deviations and convention violations, reporting a PASS, PARTIAL, or FAIL verdict.

Can I automatically check if my code follows established project patterns?

Yes, automated pattern compliance checks verify adherence to project-specific coding conventions by analyzing the implementation against established patterns. The audit identifies deviations and generates an incremental prompt pack to guide remediation for any identified gaps.

What is the best way to audit code quality and prevent regressions after implementing a feature?

Auditing code quality after feature implementation involves running the project's test suite and checking the code against Definition of Done requirements. This ensures codebase integrity by catching functional errors and confirming that established design patterns are followed.

Does the audit process provide guidance on fixing convention violations?

Yes, when convention violations or deviations from the Definition of Done are identified, the audit generates an incremental prompt pack. This pack provides targeted guidance to help developers close the gaps and achieve full compliance.

How do I run a test suite to determine compliance for a new feature?

To determine compliance, the audit executes the project's test suite while cross-referencing the implementation against a spec file. It evaluates test results alongside pattern adherence to deliver a definitive PASS, PARTIAL, or FAIL compliance verdict.

What does a PARTIAL verdict mean during a code audit?

A PARTIAL verdict indicates that the code implementation meets some, but not all, requirements of the Definition of Done or project patterns. The audit identifies these specific gaps and generates an incremental prompt pack to resolve them.