vibeos-audit

Identify and report governance, security, and quality findings during Codex project audits.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Auditing Codex projects for governance, quality, and security findings to improve project integrity and compliance.

Core Features & Use Cases

  • Focused audits on specific code changes or modules
  • WO-level and full-project audits with structured reporting
  • Governance, architecture, security, and quality review cycles with prioritized fixes

Quick Start

Initiate a focused audit on the active Codex project and report findings with prioritized actions.

Frequently Asked Questions about vibeos-audit

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

FAQPage Schema
How do I audit a Codex project for security and governance findings?

To audit a Codex project, you review code, architecture, and processes to identify governance, security, and quality findings. This process leverages shared gates and role contracts to ensure issues are prioritized, actionable, and traceable.

What is the best way to run focused code audits before implementation?

Focused code audits target specific code changes or modules before or after implementation. They utilize structured reporting and shared gates to review security and quality, generating prioritized fixes for the active project.

Can I perform a full project audit across code, architecture, and processes?

Yes, you can perform WO-level or full-project audits across code, architecture, and processes. These audits apply formal reporting cycles to identify governance, security, and quality findings with traceable actions.

How do I prioritize and report quality findings during a project audit?

Prioritizing and reporting quality findings involves leveraging shared gates and role contracts during the audit. This ensures that identified governance and security issues are actionable, traceable, and formally documented.

Does this audit workflow support WO-level reviews?

Yes, the audit workflow supports WO-level reviews alongside focused and full-project audits. It applies structured reporting cycles to evaluate governance, architecture, and security findings effectively across the project.