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

session-audit

Audit VibeOS build sessions and generate structured findings reports.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit the current or most recent VibeOS build session end-to-end to produce a comprehensive session-level report and surface follow-ups.

Core Features & Use Cases

  • Audit and close out a VibeOS session, including completed work orders, blockers, touched files, and outcomes.
  • Generate a structured session audit with findings, drift, and recommendations to guide next steps.
  • Integrate with existing docs and logs (build-log, WO-INDEX, session-state) to ensure verifiable evidence.

Quick Start

Ask the system to audit the active VibeOS session and return a structured session audit report.

Frequently Asked Questions about session-audit

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

FAQPage Schema
How do I audit a VibeOS build session to capture completed work orders and blockers?▼

To audit a VibeOS build session, the system verifies evidence against build logs and session state to capture completed work orders, blockers, touched files, and outcomes, producing a structured findings report.

When do I need a session-level audit for my build workflow?▼

A session-level audit is needed during autonomous or manual runs to verify end-to-end build outcomes and surface follow-ups. It ensures evidence aligns with prerequisites before closing out the active session.

What inputs are required to generate a session audit report with drift findings?▼

Generating a session audit report requires access to the build log, session state, WO index, and relevant anchors. These inputs allow multi-audit agents to verify evidence and identify drift.

Can I use this audit process to verify evidence against build logs automatically?▼

Yes, this audit process dispatches multi-audit agents to automatically verify evidence against logs and prerequisites. It checks touched files and outcomes to surface actionable recommendations.

What is the best way to close out a VibeOS session and surface follow-up recommendations?▼

The best way to close out a VibeOS session is running an end-to-end audit that checks the WO index and session state. It generates structured findings, drift indicators, and next-step recommendations.

Related Skills

Explore More Software Engineering Skills→
chieflatifchieflatif
2

vibeos-session-audit

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

Community
Advanced
earayuearayu
34

audit-report-refresh

Re-audits latest codebase to refresh outdated findings in prior audit reports.

Community
Advanced
arjunrattan-lab-aiarjunrattan-lab-ai

session-recap

Generate a session summary and log to a Markdown file.

Community
Intermediate
jaydubya818jaydubya818

ce:review

Orchestrate multi-agent code review and produce structured JSON findings.

Community
Advanced