bk

Diagnose Buildkite CI/CD build failures and inspect pipeline status.

9|Updated Jul 15, 2025
One-click install
npx skills add https://github.com/ivy/dotfiles --skill bk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bk
Source: https://github.com/ivy/dotfiles/tree/main/home/dot_claude/skills/bk
Command: npx skills add https://github.com/ivy/dotfiles --skill bk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Buildkite CI/CD builds can be opaque; this Skill helps diagnose failures, monitor pipelines, and retrieve logs efficiently.

Core Features & Use Cases

  • View build state and job lists for a given pipeline or build URL
  • Read and interpret failure logs to identify root causes
  • Answer high-level questions about pipeline health and recent activity

Quick Start

Ask me to investigate the latest Buildkite build for your repository.

Frequently Asked Questions about bk

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

FAQPage Schema
How do I diagnose Buildkite pipeline failures from build logs?

To diagnose Buildkite pipeline failures, this Skill parses your pipeline or build URL to fetch build states and job lists using `bk build view -o json`, then retrieves detailed logs with `bk job log -p` and `-b` to identify root causes.

Can I view Buildkite build state and job details for a specific pipeline?

Yes, you can view Buildkite build state and job details by providing a pipeline name or build URL; the Skill parses the input and queries `bk build view -o json` to return the current pipeline status and associated job lists.

How do I read Buildkite failure logs to identify the root cause of a failed CI/CD job?

Reading Buildkite failure logs is handled by the Skill, which retrieves specific job logs via the `bk job log` command with pipeline and build flags, allowing you to interpret the output and isolate the exact failure point.

What is the best way to check Buildkite pipeline health and recent build activity?

The best way to check Buildkite pipeline health is to ask this Skill to investigate recent builds; it queries the Buildkite CLI to retrieve build states and job lists, answering high-level questions about your pipeline's recent activity.

Do I need a specific Buildkite build number to investigate a CI/CD failure?

You do not need to manually locate a specific Buildkite build number; the Skill automatically parses your input to determine the pipeline and build number, then uses that to fetch the relevant build state and detailed job logs.

Why are my Buildkite logs opaque and how can I retrieve them efficiently?

Buildkite logs can be opaque, but you can retrieve them efficiently by letting this Skill parse your build URL and execute targeted `bk job log` commands to pull only the relevant pipeline and build logs for diagnosis.