vibeos-session-audit

Audit VibeOS build sessions and save structured reports to .vibeos/session-audits/.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Closeout auditing for the current or most recent VibeOS build session, ensuring a trustworthy, evidence-based review of what happened during a run.

Core Features & Use Cases

  • Structured session review: aggregates build logs, session state, planning docs, and WO references to produce a coherent audit narrative.
  • Deterministic validation: re-runs gate or verification steps to confirm the session's integrity.
  • Evidence-based reporting: saves the audit report to a designated directory and enforces explicit recommendations.

Quick Start

Initiate a full session audit on the current or most recent VibeOS build session and save the report to the audit folder.

Frequently Asked Questions about vibeos-session-audit

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

FAQPage Schema
How do I audit a VibeOS build session for closeout?

To audit a VibeOS build session for closeout, you can run an end-to-end review that aggregates build logs, session state, planning docs, and touched files into a structured report with explicit recommendations.

What is a build session audit and when do I need one?

A build session audit is an evidence-backed review of a run's integrity, needed when a session requires complete closeout and validation of planning docs, WO index, and touched files.

How do I generate an evidence-based report for VibeOS build logs?

You generate an evidence-based report for VibeOS build logs by reading session artifacts and re-running verification steps to confirm integrity before saving a structured audit to the .vibeos/session-audits/ directory.

Does the VibeOS session audit re-run verification steps automatically?

Yes, the VibeOS session audit applies deterministic validation by automatically re-running gate or verification steps to confirm the session's integrity before producing the final report.

Where are VibeOS session audit reports saved?

VibeOS session audit reports are saved to the .vibeos/session-audits/ directory as structured files containing the coherent audit narrative and explicit recommendations.

Can I audit the most recent VibeOS build session without specifying parameters?

Yes, you can audit the current or most recent VibeOS build session directly, as the process automatically targets the latest run to produce a trustworthy, evidence-backed review.