concourse-fly

To safely update a Concourse pipeline, the skill enforces read-before-write checks and generates a diff review for you to confirm exact changes before applying pipeline mutations via the fly CLI.

Fly CLI command tiering protects Concourse builds by requiring explicit authorization for high-blast-radius destructive actions, such as aborting builds or destroying pipelines, preventing unintended execution.

Yes, you can trigger Concourse jobs and monitor builds through fly by inspecting the current pipeline state first, with the skill preparing the requested action and applying guardrails to prevent accidental triggers.

The best way to inspect Concourse workers and teams is using fly commands through the skill, which retrieves current resource states and enforces review checks before executing any worker management operations.

You need explicit authorization for Concourse destructive operations when executing high-blast-radius fly commands, such as destroying pipelines, aborting builds, or managing workers, to prevent accidental data loss.