Implementation Auditor

Audit code against documentation to surface spec and ADR drift.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/Volinad/v-skills-public --skill implementation-auditor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Implementation Auditor
Source: https://github.com/Volinad/v-skills-public/tree/main/impl-auditor
Command: npx skills add https://github.com/Volinad/v-skills-public --skill implementation-auditor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Implementation Auditor identifies discrepancies between documentation and code, bridging the gap between what specs describe and what the code actually implements. It helps teams surface drift, ADR violations, and unimplemented features so owners can decide what to fix.

Core Features & Use Cases

  • Audits code against documentation to surface drift between specifications, architecture, and ADRs.
  • Reports discrepancies without automatically changing code; the Owner decides what to fix.
  • Validates ADR compliance, API contracts, data models, invariants, and state machines against the codebase.
  • Supports phased auditing (Structural Mapping, Rule Compliance, Behavioral Verification, Drift Detection) via a Phase Bridge package.
  • Run after spec-compiler (docs must be clean first) and AFTER tests pass.

Quick Start

Run the auditor against your repository after you have a clean spec-doc set and passing tests to begin drift and compliance analysis.

Frequently Asked Questions about Implementation Auditor

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

FAQPage Schema
How do I audit code against documentation to find architecture drift?

Auditing code against documentation identifies discrepancies between specs, ADRs, and the actual codebase. It surfaces API contract mismatches, data-model drift, and invariant violations by validating that implementation matches the documented specs.

What is the best way to check ADR compliance in my codebase?

Checking ADR compliance involves validating architecture decision records against the implemented code to detect violations. This skill reports discrepancies without automatically changing code, leaving the owner to decide what to fix.

Can I detect API contract mismatches and data model drift after my tests pass?

Yes, you can detect API contract mismatches and data-model drift by running the auditor after tests pass. It expects a clean spec-doc set and a corresponding codebase to successfully surface and validate structural and behavioral drift.

Do I need clean specifications and passing tests before running a code audit?

Yes, you need clean documentation and passing tests before running this code audit. Run it after a spec-compiler ensures docs are clean and tests pass to successfully surface drift and compliance issues.

How does phased auditing work for invariant validation and behavioral verification?

Phased auditing works by progressing through Structural Mapping, Rule Compliance, Behavioral Verification, and Drift Detection. A Phase Bridge package supports this process to validate invariants and state machines against the codebase.

Why should I use an implementation auditor instead of automatically fixing code drift?

Using an implementation auditor reports discrepancies for owner review rather than automatically changing code. This ensures teams retain control over deciding what drift, ADR violations, or unimplemented features to fix.