vibeos-gate

Name: vibeos-gate
Availability: InStock
Author: Chieflatif

Run automated quality gates for VibeOS code across workflow phases.

2|1|Updated Mar 9, 2026

Search Tags:#codex #quality #ci-cd #gate #gate-runner #vibeos

Ready to run

npx skills add https://github.com/chieflatif/vibeos-plugin --skill vibeos-gate

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: vibeos-gate
Source: https://github.com/chieflatif/vibeos-plugin/tree/main/plugins/vibeos/reference/codex/skills/vibeos-gate
Command: npx skills add https://github.com/chieflatif/vibeos-plugin --skill vibeos-gate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Run automated quality gates for VibeOS code to verify integrity before work-order closure.

Core Features & Use Cases

Run the shared gate runner for designated phases and provide a plain-English explanation of results.
Supports common gate phases: session_start, pre_commit, wo_exit, full_audit, post_deploy, session_end.
If requested, read .claude/quality-gate-manifest.json to summarize gate status.

Quick Start

Ask Codex to run the vibeos-gate quality gate for the current work order.

Frequently Asked Questions about vibeos-gate

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

FAQPage Schema

How do I run automated quality gates to verify code integrity before work-order closure?▼

Automated quality gates validate VibeOS code integrity before work-order closure by executing the gate-runner across designated phases like pre_commit, wo_exit, and full_audit, reporting pass/fail status, blockers, and recommendations.

What is a VibeOS quality gate and when should I run it?▼

A VibeOS quality gate is an automated validation process for code quality and compliance, applicable during session_start, pre_commit, post_deploy, and session_end workflows to verify gate status before proceeding with work-order closure.

How do I check gate status from the quality gate manifest in Codex?▼

You can check gate status by reading the .claude/quality-gate-manifest.json file, which summarizes the gate status and provides a plain-English explanation of pass/fail results, blockers, and recommendations for the selected phase.

Can I run VibeOS quality gates during the post_deploy phase?▼

Yes, VibeOS quality gates support the post_deploy phase, executing the gate-runner to validate code quality, gate status, and compliance after deployment to ensure integrity before work-order closure.

What is the best way to automate CI-CD quality checks for VibeOS code?▼

Running the shared gate-runner for designated phases like pre_commit and full_audit provides automated CI-CD quality checks for VibeOS code, reporting pass/fail status, blockers, and recommendations in plain English.

Why does my VibeOS work-order exit quality gate report blockers?▼

The wo_exit quality gate reports blockers when the gate-runner identifies code quality or compliance issues during validation, providing plain-English explanations and recommendations to resolve them before work-order closure.