rrh

Execute opt-in preflight validation stages to collect, validate, and store environment data.

3|1|Updated Oct 9, 2025

Search Tags:#validation #compliance #governance #pipeline #preflight #release readiness

Ready to run

npx skills add https://github.com/OmniNode-ai/omniclaude --skill rrh

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: rrh
Source: https://github.com/OmniNode-ai/omniclaude/tree/main/plugins/onex/skills/rrh
Command: npx skills add https://github.com/OmniNode-ai/omniclaude --skill rrh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures your environment is correctly configured and validated before critical pipeline phases, preventing errors and ensuring compliance.

Core Features & Use Cases

Opt-in Preflight Validation: Runs a sequence of checks (collect, validate, store) before side-effecting actions like pushes or deployments.
Profile-Based Strictness: Adapts validation rigor based on the pipeline phase and ticket type (e.g., default, ticket-pipeline, seam-ticket).
Governance Integration: Incorporates ticket details like ticket_id, evidence_requirements, and deployment_targets into validation.
Use Case: Before deploying a new version of your application, you can invoke this Skill to automatically verify that all necessary tools are installed, the correct branch is checked out, and the environment matches the deployment requirements, blocking the deploy if any checks fail.

Quick Start

Run the rrh skill using the ticket-pipeline profile for the current ticket ID.

Frequently Asked Questions about rrh

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

FAQPage Schema

What is preflight validation for release readiness in a deployment pipeline?▼

Preflight validation for release readiness is an opt-in process that collects environment data, validates it against governance profiles, and stores results to block pipeline deployments if compliance checks fail.

How do I validate my environment against governance rules before deploying?▼

You validate your environment by running a preflight pipeline that collects environment data, checks it against defined governance profiles and ticket contracts, and stores the validation results as an artifact.

Can I adjust validation strictness based on different pipeline phases or ticket types?▼

Yes, you can adjust validation strictness using profile-based configurations like default, ticket-pipeline, or seam-ticket, which adapt rigor based on the specific pipeline phase and ticket type.

How do ticket contracts and deployment targets factor into pipeline compliance checks?▼

Ticket contracts factor into compliance checks by integrating governance fields like ticket_id, evidence_requirements, and deployment_targets directly into the validation stages to enforce strictness control.

Does preflight release validation require any external dependencies to run?▼

No, preflight release validation requires no external dependencies, running its internal collect, validate, and store stages using only scripts and reference components provided locally.

What happens when environment validation fails during the preflight checks?▼

When environment validation fails during preflight checks, the pipeline blocks side-effecting actions like pushes or deployments and stores the failed validation results as an artifact for review.