Verified:GitHub

osdu

Analyze GitLab CI/CD test job reliability and detect flaky tests for OSDU projects.

1|Updated Nov 19, 2025

Search Tags:#quality #pipeline #flaky tests #GitLab #ci #cd #osdu

One-click install

npx skills add https://github.com/danielscholl/agent-skills --skill osdu

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: osdu
Source: https://github.com/danielscholl/agent-skills/tree/main/plugins/osdu/skills/osdu
Command: npx skills add https://github.com/danielscholl/agent-skills --skill osdu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires click, and includes scripts (resource) components.

What problem does it solve?

Tracks GitLab CI/CD test job reliability for OSDU projects, surfacing flaky tests and delivering QA metrics across pipelines.

Core Features & Use Cases

Status tracking: Monitor pass/fail status across multiple pipeline runs.
Flaky test detection: Identify tests that fail intermittently and surface reliability metrics.
Provider & stage insights: Analyze by cloud provider and test stage (unit, integration, acceptance).
Automation wrapper: Integrates with the osdu-quality CLI to automate QA workflows.

Quick Start

uv run status.py --format json --pipelines 3 --project partition

Frequently Asked Questions about osdu

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

FAQPage Schema

How do I detect flaky tests in GitLab CI/CD pipelines?▼

Flaky test detection analyzes test job results across multiple pipeline runs to identify tests that fail intermittently. Run osdu-quality analyze to surface reliability metrics and pinpoint which unit, integration, and acceptance tests fail unpredictably, then track them over time.

Can I track test reliability metrics by cloud provider in GitLab?▼

Yes. The osdu-quality analyze command segments reliability data by cloud provider and test stage, letting you compare pass rates across providers and identify provider-specific failures in your OSDU CI/CD pipelines.

What's the best way to monitor test job status across multiple pipeline runs?▼

Use osdu-quality status to track pass/fail outcomes across multiple runs with filtering by pipelines, project, and stage. Output results as JSON, markdown, or terminal display to integrate into dashboards or reports.

Do I need explicit project scoping to run OSDU quality analysis?▼

Yes. The osdu-quality commands enforce authentication and require explicit project specification to ensure proper access control and prevent accidental analysis of unintended projects.

How do I export CI/CD reliability metrics from GitLab pipelines?▼

Run osdu-quality with --format json or --format markdown to emit structured reliability data, flaky test reports, and provider breakdowns in machine-readable or documentation formats.