Trigger Buildkite builds with branch, commit, and explicit confirmation.
npx skills add https://github.com/mcncl/skill-buildkite --skill build-triggering
Please help me install this Agent Skill. Skill: build-triggering Source: https://github.com/mcncl/skill-buildkite/tree/main/skills/build-triggering Command: npx skills add https://github.com/mcncl/skill-buildkite --skill build-triggering
Automates the initiation of Buildkite builds with controlled parameters and guardrails, reducing manual steps and human error when starting pipelines.
Trigger a new build for my-pipeline on the main branch after confirming the requested options.
High-intent search queries and answers about installing and using this skill.
You can safely trigger a Buildkite build by parsing inputs for the pipeline name and branch, then providing explicit confirmation before the build starts. This enforces guardrails to prevent accidental releases on production pipelines.
Yes, you can trigger a Buildkite pipeline with a custom commit and message. The automation parses pipeline name, branch, optional commit, and message parameters to ensure reproducible builds across branches.
Automating CI workflows with Buildkite guardrails involves validating pipeline existence and branch context, then requiring explicit user confirmation before triggering builds to reduce manual steps and human error.
Yes, triggering a Buildkite build validates pipeline existence and branch context before starting. It reports results with a build URL and status to confirm the pipeline was correctly initiated.
Explicit confirmation is required to trigger a production Buildkite build to prevent accidental releases. This safety guardrail ensures deployment pipelines are only started with direct user approval.
mcnclFetch recent Buildkite builds and render a pass/fail status table.
cardano-foundationDiagnose Buildkite CI failures by listing builds, inspecting jobs, and fetching logs.
sevenbelowllcConfigure Buildkite pipelines, agents, builds, and artifacts via YAML.
Sharper-FlowAutomate release lifecycle with semver versioning and GitHub releases.
