Run any Skill in Manus with one click

vibeos-audit

Stars2

Forks1

UpdatedApril 29, 2026 at 17:28

VibeOS audit flow for Codex. Use when the user asks for a code audit, quality review, governance review, architecture review, security review, or wants a full audit cycle before or after implementation work.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

chieflatif

chieflatif/vibeos-plugin

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	vibeos-audit
description	VibeOS audit flow for Codex. Use when the user asks for a code audit, quality review, governance review, architecture review, security review, or wants a full audit cycle before or after implementation work.

VibeOS Audit

Use this skill for focused or full audits of the current project state.

Workflow

Read docs/USER-COMMUNICATION-CONTRACT.md, project-definition.json, and the relevant planning or anchor docs.
Decide whether the request is:
- focused audit of one change area
- WO-level audit
- full project audit
Refresh runtime capabilities:

bash ".vibeos/scripts/detect-runtime-capabilities.sh" --project-dir "."

Run the matching shared gates with .vibeos/scripts/gate-runner.sh.
Use available Codex-native agents or .codex/agent-contracts/*auditor*.md role contracts according to .vibeos/runtime-capabilities.json, then execute the audit phases with severity discipline. Include Flow Auditor review when the change touches user journeys, frontend/backend handoffs, auth/session continuity, data side effects, or objective fidelity. Include System Invariant Auditor review when the change touches state transitions, ownership, data integrity, retries, duplicate side effects, background jobs, webhooks, or recovery. Include Dependency Intelligence Auditor review when the change touches manifests, lockfiles, package managers, runtimes, SDKs, frameworks, auth/security/database/payment/AI packages, deployment libraries, or public-interface packages. Include Delivery Infrastructure Auditor review when the change touches CI/CD, deployment, environment/secrets, observability, smoke/health checks, rollback, runbooks, or operational scripts.
Report findings in severity order, with business impact first and concrete fixes second.
If there are no findings, say that plainly and note residual risk or verification gaps.

Rules

Findings come first; summaries come second.
Do not overstate confidence when the evidence is incomplete.
Keep accepted risks, deferred work, and blockers explicit.

More from this repository

same repository

audit

chieflatif/vibeos-plugin

Full audit cycle that dispatches audit agents (security, architecture, correctness, test quality, evidence, product drift, flow, system invariants, dependency intelligence, delivery infrastructure, red team, contract validator), applies consensus logic, and produces a composite report with actionable findings. Use when the user says "audit the code", "review everything", "check for security issues", "do a full review", or wants a comprehensive multi-perspective code review.

2026-06-152

build

chieflatif/vibeos-plugin

Autonomous build orchestrator that executes work orders end-to-end. Use when the user says "continue", "keep going", "build the next thing", "resume", "start building", or wants to make progress on the development plan. Dispatches investigator, tester, prompt-engineering, implementation, and documentation agents in sequence with two-layer quality enforcement (Layer 1 gates + Layer 2 audit agents) and error recovery, while checking for product drift and stale high-impact decisions.

2026-06-152

vibeos-autonomous

chieflatif/vibeos-plugin

Full autonomous-session override for VibeOS in Codex. Use when the user says go autonomous, stop checking in, run on your own, stay in autonomous mode, or wants VibeOS to keep building until a real blocker or decision appears.

2026-04-292

vibeos-build

chieflatif/vibeos-plugin

Autonomous VibeOS work-order execution for Codex. Use when the user says continue, resume, keep going, build the next thing, start implementing, or wants progress against the current VibeOS plan.

2026-04-292

vibeos-checkpoint

chieflatif/vibeos-plugin

Phase-boundary checkpoint and ratchet review for VibeOS in Codex. Use when the user says phase is done, milestone check, checkpoint this phase, or wants a boundary audit before starting the next phase.

2026-04-292

vibeos-comp

chieflatif/vibeos-plugin

Compact enterprise MVP mission intake for VibOS Comp. Use for competition-grade builds, enterprise design-partner MVPs, rapid production-quality prototypes, battle harness runs, or explicit VibOS Comp/VibeOS Comp requests.

2026-04-292

name	vibeos-audit
description	VibeOS audit flow for Codex. Use when the user asks for a code audit, quality review, governance review, architecture review, security review, or wants a full audit cycle before or after implementation work.

VibeOS Audit

Use this skill for focused or full audits of the current project state.

Workflow

Read docs/USER-COMMUNICATION-CONTRACT.md, project-definition.json, and the relevant planning or anchor docs.
Decide whether the request is:
- focused audit of one change area
- WO-level audit
- full project audit
Refresh runtime capabilities:

bash ".vibeos/scripts/detect-runtime-capabilities.sh" --project-dir "."

Run the matching shared gates with .vibeos/scripts/gate-runner.sh.
Use available Codex-native agents or .codex/agent-contracts/*auditor*.md role contracts according to .vibeos/runtime-capabilities.json, then execute the audit phases with severity discipline. Include Flow Auditor review when the change touches user journeys, frontend/backend handoffs, auth/session continuity, data side effects, or objective fidelity. Include System Invariant Auditor review when the change touches state transitions, ownership, data integrity, retries, duplicate side effects, background jobs, webhooks, or recovery. Include Dependency Intelligence Auditor review when the change touches manifests, lockfiles, package managers, runtimes, SDKs, frameworks, auth/security/database/payment/AI packages, deployment libraries, or public-interface packages. Include Delivery Infrastructure Auditor review when the change touches CI/CD, deployment, environment/secrets, observability, smoke/health checks, rollback, runbooks, or operational scripts.
Report findings in severity order, with business impact first and concrete fixes second.
If there are no findings, say that plainly and note residual risk or verification gaps.

Rules

Findings come first; summaries come second.
Do not overstate confidence when the evidence is incomplete.
Keep accepted risks, deferred work, and blockers explicit.