skills.rest
chieflatif
chieflatifCOMMUNITY
Explore all skills by this author →
GitHub

codex-audit

Reconcile Codex audit findings across Claude implementations.

2|1|Updated Mar 9, 2026
Search Tags:#verification#audit#codex#governance#dual-audit#vibeos
One-click install
npx skills add https://github.com/chieflatif/vibeos-plugin --skill codex-audit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: codex-audit
Source: https://github.com/chieflatif/vibeos-plugin/tree/main/plugins/vibeos/skills/codex-audit
Command: npx skills add https://github.com/chieflatif/vibeos-plugin --skill codex-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Codex audits are dispatched to provide an independent verification layer for Claude-driven work, ensuring all material findings are reconciled before closure and enforcing a zero-technical-debt policy across plans, work orders, and session endings.

Core Features & Use Cases

  • Complementary audit protocol — Claude implements while Codex audits, with support for plan, completion, session, and manual audits.
  • Mandatory reconciliation — all findings must be reconciled and tracked, ensuring no undisclosed debt before closure.
  • Use cases include plan approvals, WO closures, and session end validations, plus on-demand audits for ongoing governance and risk mitigation.

Quick Start

Provide a codex-audit command to run an independent audit on a draft WO or session.

Frequently Asked Questions about codex-audit

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

FAQPage Schema
How do I run an independent code audit to verify Claude implementations?▼

You can run an independent code audit by dispatching a Codex audit to verify Claude-driven work, which applies an independent verification layer to reconcile findings before closure.

What is a dual-audit reconciliation workflow for technical debt?▼

A dual-audit reconciliation workflow identifies and resolves technical findings from Codex audits across Claude implementations, enforcing a zero-technical-debt policy before any plan or session closure.

When do I need to perform a Codex audit during software development?▼

You need a Codex audit during plan approvals, work order closures, session end validations, or on-demand to mitigate governance risks and ensure no undisclosed technical debt remains.

How do I reconcile technical findings from automated code audits?▼

You reconcile technical findings by applying a mandatory workflow that tracks all audit results through an audit broker, ensuring every material finding is resolved before final closure.

Do I need automated context gathering for a code audit?▼

Yes, automated context gathering is required to support the audit broker and mandatory reconciliation workflow, ensuring all technical findings are properly identified and tracked for zero debt.

What is the best way to enforce a zero-technical-debt policy across work orders?▼

The best way to enforce zero technical debt is using a complementary audit protocol where Claude implements while Codex audits, requiring mandatory reconciliation of all findings before closure.

Related Skills

Explore More Software Engineering Skills→
vinhnxvvinhnxv
6

cc-inspect

Inspect Claude Code runtime state and plugin configuration via Bash script.

Community
Intermediate
nicsuzornicsuzor

dump

Close a work session and emit a structured handover artifact.

Community
Intermediate
chieflatifchieflatif
2

session-audit

Audit VibeOS build sessions and generate structured findings reports.

Community
Advanced
AsiaOstrichAsiaOstrich
70

discover

Assess project health, architecture, and risks in existing codebases.

Community
Intermediate