pilot-cd-gate

Generate cub-scout compare source-truth evidence for Pilot CD pre-deploy gates.

14|Updated Jan 17, 2026
One-click install
npx skills add https://github.com/confighub/cub-scout --skill pilot-cd-gate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pilot-cd-gate
Source: https://github.com/confighub/cub-scout/tree/main/skills/pilot-cd-gate
Command: npx skills add https://github.com/confighub/cub-scout --skill pilot-cd-gate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you decide whether a release is safe to promote by turning cub-scout's structured, read-only Kubernetes/GitOps evidence into a clear pre-deploy gate outcome for Pilot, without cub-scout making any authority calls or PASS/BLOCK decisions itself.

Core Features & Use Cases

  • Pre-deploy evidence for CD decisions: Produces strategy-anchored evidence via compare source-truth that Pilot can use to render a verdict for “should this deploy go?”.
  • Typed, durable audit artifacts (receipts): Optionally generates and saves a fingerprinted in-toto receipt via receipt verify for attachable, immutable proof and CI gating.
  • Strategy-enforced source-truth checks: Requires a caller-declared strategy (git/helm/kustomize/oci + argo/flux variants) so the gate is conformance-based rather than guesswork.
  • Explicit missing-evidence reporting: Surfaces proof gaps and safe next actions via structured outputs so operators know what to fix when evidence is incomplete.

Quick Start

Ask Pilot to gate the apply by running cub-scout compare source-truth <kind>/<name> -n <ns> with an explicit --strategy <s> and JSON output, then have Pilot use the evidence to decide PASS/WATCH/ASK/BLOCK.

Frequently Asked Questions about pilot-cd-gate

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

FAQPage Schema
How do I gate CD deploys using Kubernetes GitOps evidence?

You gate CD deploys by running cub-scout compare source-truth with an explicit strategy like git or helm, generating evidence that Pilot uses to render a PASS or BLOCK verdict for the deploy.

What is source-truth strategy comparison for Argo or Flux deployments?

Source-truth strategy comparison validates Kubernetes live state against a declared GitOps strategy like Argo or Flux before promoting a release, ensuring conformance-based CD gating rather than guesswork.

Do I need to specify a GitOps strategy for Kubernetes pre-deploy gating?

Yes, you must provide a caller-declared strategy such as git, helm, kustomize, or oci with argo or flux variants so the gate performs conformance-based checks rather than guessing your deployment state.

How do I generate immutable audit receipts for CI gating?

You generate immutable audit receipts by using the optional receipt verify feature to create and save a fingerprinted in-toto receipt, providing attachable typed artifacts for CI gating and durable proof.

Why does my Kubernetes CD gate report incomplete evidence?

A CD gate reports incomplete evidence when source-truth checks find missing data, surfacing structured proof gaps and safe next actions so operators know exactly what to fix before proceeding.

Can I use cub-scout evidence to block unsafe Kubernetes promotions automatically?

cub-scout generates read-only structured evidence without making authority calls itself, allowing Pilot to consume the data and automatically block unsafe Kubernetes promotions based on strategy-anchored decisions.