deep-audit-cross-codex

Runs two isolated full-coverage audits against one inventory and reconciles disagreements with evidence.

5|9|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/ajenchen/design-system --skill deep-audit-cross-codex-ajenchen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deep-audit-cross-codex
Source: https://github.com/ajenchen/design-system/tree/main/.agents/skills/deep-audit-cross-codex
Command: npx skills add https://github.com/ajenchen/design-system --skill deep-audit-cross-codex-ajenchen

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Single-pass code and design-system audits can miss findings or produce unverified claims, and there is no trustworthy way to confirm that a review actually covered everything. This Skill runs a complete no-sampling primary audit plus a genuinely independent second audit from a different provider, then reconciles the two with evidence so no finding is accepted on trust alone. ## Core Features & Use Cases - Dual isolated audits: Executes a complete primary audit and an independent peer audit in a separate read-only context against the identical frozen inventory and rubric. - Evidence-based reconciliation: Compares findings dimension by dimension, reproduces every claim against source, and preserves disagreements instead of resolving them by vote. - Fail-closed governance: Returns REVIEW-BLOCKED whenever coverage is incomplete, identity is missing, isolation is absent, or the worktree drifts, never fabricating a PASS. - Use Case: Before a design-system release, run this Skill to audit every component, rule, and test with two independent providers, then receive a report of verified findings, rejected claims, and residual risk. ## Quick Start Run a deep cross-provider audit of this repository with full coverage and reconcile the independent findings.

Frequently Asked Questions about deep-audit-cross-codex

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

FAQPage Schema
How do I run an independent cross-provider code audit?

Freeze the inventory and rubric, run a complete primary audit, then send the same inputs without conclusions to a different provider in a separate read-only context. Reconcile both coverage ledgers dimension by dimension and verify every claim against source evidence.

What makes a second audit count as independent review?

The peer must use a different provider than the author and primary, run in an isolated read-only context, and receive the frozen inputs without seeing primary conclusions. Same-provider workers or renamed adapters do not qualify as independent peers.

Why does the audit return REVIEW-BLOCKED instead of results?

REVIEW-BLOCKED occurs when coverage is incomplete, provider identity is missing, isolation is not evidenced, the transport is unavailable, or worktree fingerprints changed. The workflow fails closed and never reports PASS without complete evidence.

Can the audit use sampling or representative subsets of files?

No. Every rubric dimension must record all files inspected, findings with path and line evidence, deterministic checks run, and explicit zero-finding evidence. Sampling, skipped checks, or unrecorded omissions make the pass incomplete.

How are disagreements between the two audit passes resolved?

Each finding is independently verified by locating the governing canonical source, reproducing the claimed fact, and scanning for counterexamples. Disagreements are preserved in a comparison record rather than resolved by vote or authority.