audit

Audit health-check artifacts and runtime state for staleness and quality gaps.

Updated Apr 27, 2026
One-click install
npx skills add https://github.com/vTRKA/supervibe --skill audit-vtrka
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit
Source: https://github.com/vTRKA/supervibe/tree/main/skills/audit
Command: npx skills add https://github.com/vTRKA/supervibe --skill audit-vtrka

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit prevents stale, unverified, or low-quality project changes by checking that health-check signals and evidence-backed artifacts are present before an agent proceeds.

Core Features & Use Cases

  • Evidence-based review: Reads registry, memory index state, confidence/effectiveness logs, receipts, and recent context to produce a bounded audit decision.
  • Health and readiness gating: Detects stale references, coverage gaps, weak artifacts, stale agent/rule verifications, excessive override rates, and effectiveness concerns.
  • Structured, non-mutating output: Emits a concrete PASS/FAIL/PARTIAL/BLOCKED/ADVISORY handoff with cited evidence, confidence caps, blockers, and nextAction, without mutating production artifacts.

Quick Start

Ask your AI to audit the project for stale or weak evidence by running /supervibe-audit and stopping once the structured health report is returned.

Frequently Asked Questions about audit

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

FAQPage Schema
How do I audit my project for stale context before an AI agent starts coding?

Project audit ensures AI-assisted coding proceeds only with evidence-backed context by checking health-check artifacts and runtime state for staleness. It detects coverage gaps, stale references, and weak artifacts, emitting a bounded PASS, FAIL, PARTIAL, BLOCKED, or ADVISORY decision with confidence caps.

When should I run an agent readiness audit during a development session?

You should trigger a project audit at session start, after substantial file changes, or when an agent reports stale-context blockers. This ensures project memory, indexing, receipts, and validators are checked for staleness and quality gaps before any AI-assisted coding proceeds.

Does the project audit process modify my production code or files?

No, the project audit is strictly non-mutating and does not modify production artifacts. It emits a structured health report with cited evidence, confidence caps, blockers, and nextAction recommendations, providing a bounded decision without altering your codebase.

What specific evidence and artifacts are checked during a project health audit?

A project health audit reads registry entries, memory index state, confidence and effectiveness logs, receipts, and recent context. It detects stale references, coverage gaps, weak artifacts, stale agent verifications, and excessive override rates to produce a bounded audit decision.

Why does my AI agent report stale-context blockers despite recent file changes?

Stale-context blockers occur when health-check artifacts, memory index state, or evidence receipts are outdated after substantial file changes. Running a project audit verifies findings with reproducible evidence, identifies coverage gaps, and clears blockers by emitting a structured health report with confidence caps.