working-with-release-gating

Evaluates release gates and drives the release lifecycle on the Fianu compliance platform.

1|Updated Jun 11, 2026
One-click install
npx skills add https://github.com/fianulabs/fianu-skills --skill working-with-release-gating-fianulabs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: working-with-release-gating
Source: https://github.com/fianulabs/fianu-skills/tree/main/skills/working-with-release-gating
Command: npx skills add https://github.com/fianulabs/fianu-skills --skill working-with-release-gating-fianulabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Determining whether a release passes its compliance gates requires querying multiple Fianu API endpoints, interpreting per-control attestation results, and handling edge cases like unscanned evidence or annotation overrides. This Skill consolidates the runtime gate evaluation and release lifecycle endpoints into one operational guide. ## Core Features & Use Cases - Runtime Gate Evaluation: Query the gates and required controls that apply to an asset at a specific commit via GET /assets/:asset/gates/policies/controls. - Gate Attestation Summary: Read paged attestation roll-ups per gate with filters for result, status, date range, and gate version. - Release Lifecycle Management: Create releases, check status, and trigger evidence scans, resyncs, and modifiers through the /releases endpoints. - Use Case: A release manager asks why a release is blocked. The Skill walks the release's child assets, fetches required controls per gate at the commit, checks each control's attestations, and reports the specific failing controls rather than just the gate name. ## Quick Start Check whether release uuid abc-123 passes its gates and list any failing controls blocking it.

Frequently Asked Questions about working-with-release-gating

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

FAQPage Schema
How do I check if a release passes its compliance gates?▼

Query GET /assets/releases/:uuid/status for the release's lifecycle state and per-gate results. For detail, fetch the required controls per gate at the release's commit and check each control's attestations for pass, not required, or excused results.

How to find which controls a gate requires at a specific commit?▼

Call GET /assets/:asset/gates/policies/controls with the commit query parameter to get the runtime view of gates and their required controls. Omitting commit returns config-level data instead of the asset's actual evaluation.

Why does a gate show blocked when evidence was never scanned?▼

A release with no evidence has no attestations to roll up, so it is unevaluated rather than failed. Trigger POST /assets/releases/:uuid/evidence/scan first, then read the status before reporting any pass or fail conclusion.

Can a failing control still pass a gate?▼

Yes, a failing control excused by an annotation passes the gate. When explaining why a gate passed, reflect the annotation rather than reporting the raw fail result alone.

What is the difference between runtime and config gate views?▼

The runtime view (GET /assets/:asset/gates/policies/controls?commit=) evaluates gates against a real asset at a commit. The config view (GET /console/gates/:gate_entity_key/policies/controls) lists required controls independent of any asset or commit.