tb-sem

Analyze Semaphore CI pipeline failures to identify root causes and flaky tests.

Updated Mar 7, 2026
One-click install
npx skills add https://github.com/productiveio/cli-toolbox --skill tb-sem
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tb-sem
Source: https://github.com/productiveio/cli-toolbox/tree/main/crates/tb-sem
Command: npx skills add https://github.com/productiveio/cli-toolbox --skill tb-sem

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps developers and operations teams quickly identify and understand the root causes of CI/CD pipeline failures, reducing debugging time and improving deployment reliability.

Core Features & Use Cases

  • Pipeline Triage: Automatically analyzes failed pipelines to surface key error messages and identify flaky tests.
  • Test Flakiness Detection: Pinpoints tests that intermittently fail across different runs.
  • Deploy Analysis: Tracks recent deployments and checks for overlaps that might indicate integration issues.
  • Use Case: When a critical pipeline fails, use this Skill to get an immediate summary of the failure, identify the specific test that broke, and check if recent deployments might be related, all without manually sifting through logs.

Quick Start

Use tb-sem triage to analyze the latest failed run for the 'api' project.

Frequently Asked Questions about tb-sem

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

FAQPage Schema
How do I triage Semaphore CI pipeline failures automatically?

To triage Semaphore CI pipeline failures automatically, you can query pipeline logs and job details to identify root causes, flaky tests, and deploy overlaps without manual log sifting.

How does flaky test detection work in CI/CD pipelines?

Flaky test detection in CI/CD pipelines works by analyzing pipeline run histories to pinpoint tests that intermittently fail across different executions, helping isolate environmental or timing issues.

Can I analyze recent deployments for overlaps causing CI pipeline failures?

Yes, you can analyze recent deployments to check for overlaps that might indicate integration issues, providing immediate context for why a critical CI/CD pipeline failed.

Do I need Semaphore CI API access to debug test failures?

Yes, you need Semaphore CI API access for data retrieval and analysis, as the automated triage process queries pipeline logs and job details directly through the API.

What is the best way to classify CI/CD errors from pipeline logs?

The best way to classify CI/CD errors from pipeline logs is using automated triage tools that surface key error messages and identify root causes directly from job details.

Why does my CI/CD pipeline fail intermittently during deployments?

CI/CD pipelines fail intermittently during deployments due to flaky tests or overlapping deployment windows, which can be identified by tracking recent deployments and checking for integration overlaps.