slowest-tests

Find the top-N slowest test files from BuildKite CI runs.

95.3k|4.9k|Updated Apr 14, 2021
One-click install
npx skills add https://github.com/oven-sh/bun --skill slowest-tests
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: slowest-tests
Source: https://github.com/oven-sh/bun/tree/main/.claude/skills/slowest-tests
Command: npx skills add https://github.com/oven-sh/bun --skill slowest-tests

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Find the top-N slowest test files in CI from a recent BuildKite run, optionally posting the results to a Slack channel as a formatted table. Use when asked to find slow CI tests, "what's making CI slow", or to post a slow-test report to Slack.

Core Features & Use Cases

  • Gather CI timing data from BuildKite logs for multiple tests and compute the max duration per file across platforms.
  • Post summaries to Slack with a formatted table, including per-file durations and platform tags.
  • Use cases: diagnose CI slowness in merged PR builds and craft targeted optimizations.

Quick Start

Run the script to fetch the latest finished BuildKite CI data and output the top-N slowest tests; optionally post results to Slack.

Frequently Asked Questions about slowest-tests

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

FAQPage Schema
How do I find the slowest tests in my BuildKite CI pipeline?

You can identify CI bottlenecks by listing slow tests from recent BuildKite runs. The Skill gathers timing data from BuildKite logs, computes the maximum duration per file across platforms, and outputs a ranked list of the slowest test files.

Can I automatically post slow test reports to Slack?

Yes, the Skill optionally posts slow test reports to Slack. It formats the top-N slowest test files into a table with per-file durations and platform tags, then sends the summary directly to a specified Slack channel.

How are CI test durations calculated across different platforms?

Test durations are calculated by gathering timing data from BuildKite CI logs and computing the maximum duration per test file across different platforms. This ensures the reported bottleneck reflects the worst-case performance for each test.

What is the best way to diagnose CI slowness in merged PR builds?

The best way to diagnose CI slowness in merged PR builds is to analyze BuildKite CI logs to find the top-N slowest test files. This highlights the specific tests causing delays so you can plan targeted optimizations.