audit

Identify and document differences between two implementations to ensure parity.

10|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/cookys/autopilot --skill audit-cookys
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit
Source: https://github.com/cookys/autopilot/tree/main/skills/audit
Command: npx skills add https://github.com/cookys/autopilot --skill audit-cookys

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured audit process to identify differences between two implementations, ensuring parity and traceability across versions or platforms.

Core Features & Use Cases

  • Phase-driven analysis: defines scopes, phases, and criteria to surface parity gaps and intentional design divergence.
  • Parallel comparison methodology: enables side-by-side evaluation, traceable findings, and reproducible results.
  • Actionable remediation planning: classifies findings by severity and prescribes prioritized fixes to restore parity.

Quick Start

Compare two implementations by running an audit against the target and source to surface parity gaps and mismatches.

Frequently Asked Questions about audit

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

FAQPage Schema
How do I audit code parity between two different implementations?

To audit code parity, you run a parallel comparison against a defined source and target to surface mismatches. This structured methodology records the presence, correctness, and completeness of features to identify parity gaps.

What is the best way to identify intentional design divergence during a refactor?

Identifying design divergence during a refactor requires a phase-driven analysis that defines scopes and criteria. This approach classifies findings by severity to distinguish intentional divergence from actual parity gaps.

How do I document differences for a cross-version technology migration?

Documenting differences for a technology migration involves applying a structured audit process to compare implementations. It generates traceable findings and actionable remediation plans by evaluating feature correctness side-by-side.

Can I use this audit methodology to validate spec alignment without specific dependencies?

Yes, validating spec alignment requires no external dependencies. You need a clear scope, a defined source and target, and the phase-driven comparison methodology to evaluate completeness and ensure specification alignment.

How are parity gaps prioritized when comparing two codebases?

Parity gaps are prioritized through actionable remediation planning that classifies findings by severity. This prescribes prioritized fixes to restore parity, ensuring critical mismatches between implementations are addressed first.