pipeline-monitor

Analyze CI/CD pipeline build success rates, flaky tests, and duration trends.

1|Updated Jan 26, 2026

Search Tags:#testing #ci/cd #performance #monitoring #pipeline #builds

Ready to run

npx skills add https://github.com/manastalukdar/claude-devstudio --skill pipeline-monitor

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pipeline-monitor
Source: https://github.com/manastalukdar/claude-devstudio/tree/main/skills/pipeline-monitor
Command: npx skills add https://github.com/manastalukdar/claude-devstudio --skill pipeline-monitor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps you monitor your Continuous Integration and Continuous Deployment (CI/CD) pipelines by tracking build success rates, identifying flaky tests, and analyzing performance trends.

Core Features & Use Cases

Build Success Rate Tracking: Monitor the percentage of successful builds over time.
Flaky Test Identification: Pinpoint tests that fail intermittently, indicating instability.
Performance Trend Analysis: Track build durations to detect performance degradations.
Use Case: A development team notices an increase in build failures. They use this Skill to quickly identify that a specific test is failing intermittently (flaky) and that build times have also increased, allowing them to prioritize fixing the flaky test and investigating performance bottlenecks.

Quick Start

Analyze the CI/CD pipeline for the current repository.

Frequently Asked Questions about pipeline-monitor

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

FAQPage Schema

How do I track CI/CD build success rates and find flaky tests?▼

To track CI/CD build success rates and find flaky tests, this Skill analyzes pipeline logs to monitor successful build percentages over time and pinpoint tests that fail intermittently. It works across GitHub Actions, GitLab CI, and CircleCI to indicate test instability.

Does CI/CD pipeline monitoring work with GitHub Actions, GitLab CI, and CircleCI?▼

Yes, CI/CD pipeline monitoring works with GitHub Actions, GitLab CI, and CircleCI. The Skill analyzes build performance, identifies flaky tests, and tracks duration trends across these specific continuous integration platforms to provide actionable insights.

What is a flaky test and how does it impact build duration trends?▼

A flaky test fails intermittently, indicating instability in your pipeline. Identifying flaky tests is crucial because they disrupt build duration trends and overall pipeline stability, allowing teams to prioritize fixes and investigate performance bottlenecks effectively.

How do I analyze CI/CD pipeline performance for the current repository?▼

To analyze CI/CD pipeline performance for the current repository, you initiate a quick start analysis that parses logs efficiently using caching to minimize token usage. This provides actionable insights into build success rates, flaky tests, and duration trends.

What's the best way to minimize token usage when parsing CI/CD build logs?▼

The best way to minimize token usage when parsing CI/CD build logs is to leverage caching and efficient log parsing techniques. This Skill uses these methods to track build success rates and identify flaky tests while providing actionable pipeline insights.

Why does my CI/CD pipeline have intermittent build failures and increased build times?▼

Your CI/CD pipeline has intermittent build failures and increased build times likely due to flaky tests and performance degradations. By analyzing build duration trends and identifying intermittently failing tests, you can pinpoint instability and prioritize fixing bottlenecks.