askill
debugging-failed-builds

debugging-failed-buildsSafety 95Repository

Debug failed Buildkite builds by watching builds, finding failed jobs, reading logs, and identifying errors. Use when a build has failed or you need to diagnose CI failures.

5 stars
1.2k downloads
Updated 2/20/2026

Package Files

Loading files...
SKILL.md

Debugging Failed Builds

Diagnose and fix failed Buildkite builds.

Load skills: using-buildkite

Workflow

1. Watch the Build

Wait for the build to finish (or start failing):

bk build watch -p pipeline -b my-branch

2. Find Failed Jobs

bk build list -p org/pipeline --branch my-branch --limit 1 -o json | jq '.[0].jobs[] | select(.state == "failed" or .state == "timed_out") | {id, name, web_url}'

3. Read Job Logs

For each failed job, fetch the log and look for errors:

bk job log <job-id> -p org/pipeline -b <build-number> --no-timestamps | tail -n 200

4. Search for Errors

bk job log <job-id> -p org/pipeline -b <build-number> --no-timestamps | grep -i error -C 3

5. Check for Test Failures

If the failed job ran tests, get the test run IDs and hand off to the debugging-failed-tests skill:

ruby scripts/test_runs.rb org/pipeline <build_number>

Install

Download ZIP
Requires askill CLI v1.0+

AI Quality Score

72/100Analyzed 2/22/2026

A practical skill for debugging Buildkite CI failures with a clear 5-step workflow. Provides actionable commands for watching builds, finding failed jobs, reading logs, and searching for errors. Good structure and safety (read-only ops), but limited completeness due to missing prerequisites and setup details. Tags include CI/CD but incorrectly reference GitHub Actions for a Buildkite-focused skill. Moderate internal-only signal - appears reusable."

95
80
75
55
70

Metadata

Licenseunknown
Version-
Updated2/20/2026
Publisherblaknite

Tags

ci-cdgithub-actionstesting