ci-detective

Classify CI failures on PRs as pre-existing or introduced using GitHub Actions and GitLab CI.

2|Updated Mar 11, 2026

Search Tags:#automation #gitlab-ci #github-actions #ci #ci-failures #ci-detective

One-click install

npx skills add https://github.com/mdelapenya/coding-skills --skill ci-detective

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: ci-detective
Source: https://github.com/mdelapenya/coding-skills/tree/main/skills/ci-detective
Command: npx skills add https://github.com/mdelapenya/coding-skills --skill ci-detective

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

CI Detective helps engineering teams quickly determine if a PR failure is pre-existing or introduced by the change, by cross-referencing failing tests with other recent runs.

Core Features & Use Cases

Detect the CI system used by the repository and load platform-specific references (GitHub Actions or GitLab CI).
Gather failing jobs and tests from the current PR run, then fetch recent completed runs on other branches for comparison.
Classify failures as pre-existing or introduced by the PR and present a concise root-cause report with suggested next steps.

Quick Start

Invoke the skill on a PR to compare current CI failures with recent runs and determine their origin.

Frequently Asked Questions about ci-detective

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

FAQPage Schema

How do I check if a CI failure on a pull request is pre-existing?▼

You can determine if a CI failure is pre-existing by cross-referencing failing tests from your current PR run with recent completed CI runs on other branches. This comparison classifies whether the failures were introduced by the PR or already existed in the codebase.

Does CI failure detection work with both GitLab CI and GitHub Actions?▼

Yes, CI failure detection supports both GitHub Actions and GitLab CI. The tool detects the repository's CI platform and loads platform-specific references to retrieve logs and compare failing test runs across different branches.

What is the process to diagnose PR CI failures across different branches?▼

Diagnosing PR CI failures involves detecting the CI system, gathering failing tests from the current PR run, fetching recent completed runs from other branches for comparison, and classifying the failures as either pre-existing or introduced by the PR.

Can I automatically classify GitHub Actions test failures as introduced or pre-existing?▼

Yes, you can automatically classify GitHub Actions test failures by cross-referencing failing tests with other recent runs. The system compares current PR runs against recent completed branch runs to determine whether failures were introduced by the pull request or already existed.

Why do I need to cross-reference failing tests with recent completed runs?▼

Cross-referencing failing tests with recent completed runs is needed to accurately determine a failure's origin. By comparing PR failures against runs from other branches, you distinguish between pre-existing issues and regressions newly introduced by the pull request.