ci-deploy-preflight

Name: ci-deploy-preflight
Availability: InStock
Author: edri2or

Insert a CI pre-flight step that curls the runtime endpoint and validates the contract.

Updated Aug 27, 2026

Search Tags:#security #validation #deploy #github-actions #preflight #ci #runtime-contract

Ready to run

npx skills add https://github.com/edri2or/ripo-skills-main --skill ci-deploy-preflight

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ci-deploy-preflight
Source: https://github.com/edri2or/ripo-skills-main/tree/main/exported-skills/ci-deploy-preflight
Command: npx skills add https://github.com/edri2or/ripo-skills-main --skill ci-deploy-preflight

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deployments often silently degrade when the runtime contracts (endpoint, authentication, status, and scope) are not enforced in CI. This Skill inserts a pre-flight check to curl the actual runtime resource with the same headers and credentials, surfacing an actionable remediation message when violations occur.

Core Features & Use Cases

Inserts a pre-flight step into the CI workflow before deploy that hits the runtime endpoint using the same headers and credentials the deployed system will use.
Emits precise ::error:: messages naming the credential, the HTTP status, and the exact remediation required to fix the contract.
Provides end-to-end guardrails and testing guidance to ensure contract validation occurs before production releases.

Quick Start

Insert the pre-flight step into your CI workflow to validate the runtime contract before deployment.

Frequently Asked Questions about ci-deploy-preflight

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

FAQPage Schema

How do I validate runtime contracts before deploying in CI?▼

A pre-flight CI check validates runtime contracts by curling the actual endpoint with identical headers and credentials before deployment, emitting a precise error message naming the credential, HTTP status, and remediation required when violations occur.

How do I prevent silent runtime degradation from reaching production?▼

Preventing silent runtime degradation from reaching production requires a CI gate that tests the endpoint, authentication shape, expected HTTP status, and minimum scope before deploy, surfacing actionable remediation messages when violations occur.

Can I use GitHub Actions to check API endpoint authentication and status before deploy?▼

Yes, you can use GitHub Actions to check API endpoint authentication and status before deploy by inserting a pre-flight step that hits the runtime resource with the same credentials, failing with an error message when the HTTP status or scope is violated.

What is a pre-flight check for runtime contracts in CI?▼

A pre-flight check for runtime contracts in CI is a validation step that pins down the endpoint, authentication shape, expected HTTP status, and minimum scope, curling the runtime resource to prevent silent degradation from reaching production.

Why do my deployments silently degrade when runtime contracts are not enforced?▼

Deployments silently degrade when runtime contracts are not enforced in CI because the endpoint, authentication, status, and scope are never validated against the actual resource before the production release occurs.

Do I need specific dependencies to run a pre-flight curl validation in my workflow?▼

No specific dependencies are required to run a pre-flight curl validation in your workflow, as the skill operates without external dependencies to insert the CI gate that tests your runtime endpoint and credentials.