gate

Automate quality-gate checks for work-order lifecycle phases.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the execution and interpretation of quality gates across work-order lifecycles to ensure standards are met before progression.

Core Features & Use Cases

  • Run gates for a specific lifecycle phase such as pre_commit, wo_exit, full_audit, post_deploy, session_start, and session_end, and report results in plain English.
  • Manage gate configurations by listing, enabling, and disabling gates via a manifest to tailor checks for your workflow.
  • Clear guidance and remediation by distinguishing blocking failures from advisories and providing recommended next steps.

Quick Start

Run gates for the pre_commit phase to verify code quality before committing.

Frequently Asked Questions about gate

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

FAQPage Schema
How do I automate quality-gate checks for a work-order lifecycle?

Automating quality-gate checks for a work-order lifecycle is done by reading the gate manifest and executing the gate runner script to enforce required standards. The system produces plain-English results distinguishing blocking failures from advisories.

What lifecycle phases can I run pre-commit quality gates on?

Pre-commit quality gates can be run across multiple lifecycle phases including pre_commit, wo_exit, full_audit, post_deploy, session_start, and session_end. Each phase executes configured checks to ensure progression standards are met.

How do I list, enable, or disable code quality gates for my workflow?

Listing, enabling, or disabling code quality gates is managed through subcommands that interact with the gate manifest. This allows you to tailor checks specifically for your workflow progression requirements.

How are blocking failures distinguished from advisory warnings during a gate run?

Blocking failures are distinguished from advisory warnings during a gate run by evaluating the manifest outcomes and producing plain-English results. This provides clear guidance and recommended remediation steps before progression.

Do I need a specific manifest configuration to run a full audit quality gate?

Running a full audit quality gate requires reading an existing gate manifest configuration to execute the runner script. The manifest dictates which specific checks are enabled or disabled for the audit phase.