speed-budgets

Define and enforce test speed budgets across layered validation suites.

9|2|Updated Jun 6, 2026
One-click install
npx skills add https://github.com/app-vitals/shipwright --skill speed-budgets
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speed-budgets
Source: https://github.com/app-vitals/shipwright/tree/main/plugins/shipwright/skills/speed-budgets
Command: npx skills add https://github.com/app-vitals/shipwright --skill speed-budgets

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents slow, mis-layered tests from undermining fast feedback loops by turning execution speed into an explicit quality gate.

Core Features & Use Cases

  • Layered Speed Budgets: Defines default p95 targets, hard caps, and suite-wall limits for unit, integration, smoke, and E2E tests.
  • Mis-layer Detection: Uses runtime thresholds to flag tests that behave like a higher-cost layer than their label suggests.
  • CI Enforcement Guidance: Recommends runner timeouts and job caps so new tests cannot drift past acceptable limits unnoticed.
  • Use Case: A team auditing a failing test suite can classify slow tests, tighten budgets, and decide whether each test should be promoted, rebuilt, or moved to a different layer.

Quick Start

Use the speed-budgets skill to evaluate your repository’s test layers against the default runtime budgets and CI enforcement targets.

Frequently Asked Questions about speed-budgets

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

FAQPage Schema
How do I enforce test speed budgets in CI pipelines?

Enforce test speed budgets in CI by setting per-test p95 targets, hard caps, and suite-wall limits. Apply runner timeouts and job caps to prevent new tests from drifting past acceptable limits and stalling pipelines.

Why does my unit test suite take so long to run?

Your unit test suite may run slowly due to mis-layered tests. Runtime thresholds flag tests behaving like a higher-cost layer than their label suggests, indicating they should be rebuilt or moved to integration, smoke, or E2E pipelines.

What are runtime budgets for unit, integration, and E2E tests?

Runtime budgets are explicit execution speed limits for layered validation suites. They include default p95 targets and hard caps for unit, integration, smoke, and E2E tests to keep feedback loops fast and trustworthy.

How do I detect mis-layered tests in a repository?

Detect mis-layered tests by evaluating runtime thresholds against default budgets. Flag tests that behave like a higher-cost layer than their label suggests, then decide whether each test should be promoted, rebuilt, or moved to a different layer.

Can I use runtime budgets to audit a failing test suite?

Yes, you can audit a failing test suite by classifying slow tests against default runtime budgets. Tighten p95 targets and hard caps to classify tests and determine whether each should be promoted, rebuilt, or moved to a different validation layer.

What is the best way to set timeout enforcement for test automation?

Set timeout enforcement by defining hard caps and suite-wall limits for test automation. Use CI guardrail design to recommend runner timeouts and job caps so new tests cannot drift past acceptable limits unnoticed.