vapa-audit

Validate AI-executed code changes against proposals and architectural constraints.

1|1|Updated May 8, 2026
One-click install
npx skills add https://github.com/insentek/VAPA --skill vapa-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vapa-audit
Source: https://github.com/insentek/VAPA/tree/main/skills/vapa-audit
Command: npx skills add https://github.com/insentek/VAPA --skill vapa-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the uncertainty of whether an AI-generated implementation is truly ready for production by providing an independent, evidence-based validation gate between execution and human review.

Core Features & Use Cases

  • Traceability Verification: Ensures implementation strictly adheres to approved proposals, acceptance criteria, and design constraints.
  • Automated Audit Reporting: Generates a structured VAPA_AUDIT.md report detailing findings, test results, and UI evidence.
  • Verdict-Driven Workflow: Provides clear status indicators like READY_FOR_PR or NEEDS_REVISION to guide the next steps in the development lifecycle.

Quick Start

Ask the agent to run the vapa-audit skill to validate the current execution workspace and determine if the changes are ready for a pull request.

Frequently Asked Questions about vapa-audit

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

FAQPage Schema
How do I validate AI-generated code for PR readiness?

You can validate AI-generated code for PR readiness by running an audit skill that checks execution workspaces against approved proposals and test reports. It verifies implementation integrity and outputs a formal READY_FOR_PR or NEEDS_REVISION verdict.

What is traceability verification for agent-executed code?

Traceability verification for agent-executed code ensures that AI implementations strictly adhere to approved proposals, acceptance criteria, and design constraints. It acts as an evidence-based validation gate before human review.

How do I generate an automated audit report for AI code changes?

To generate an automated audit report for AI code changes, the validation process analyzes state files, execution logs, and evidence directories. It outputs a structured VAPA_AUDIT.md report detailing findings and test results.

Do I need state files and execution logs to validate my project workspace?

Yes, you need access to state files, execution logs, and evidence directories to validate your project-local execution workspace. These inputs are required to verify implementation integrity and produce a formal audit verdict.

What is the best way to check if AI implementation is ready for production?

The best way to check if an AI implementation is ready for production is to use an independent validation gate that compares code changes against architectural constraints. It provides clear status indicators like READY_FOR_PR or NEEDS_REVISION to guide next steps.

Why does my AI code audit return a NEEDS_REVISION status?

Your AI code audit returns a NEEDS_REVISION status when the implementation fails to strictly adhere to approved proposals, test reports, or architectural constraints. It indicates the changes require corrections before moving to human review.