debugging-e2e-tests

Analyze failed Opik E2E tests and propose fixes.

Updated Aug 27, 2026

Search Tags:#debugging #CI/CD #failure analysis #E2E testing #Opik

Ready to run

npx skills add https://github.com/jimmy071919/iiii-project --skill debugging-e2e-tests

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debugging-e2e-tests
Source: https://github.com/jimmy071919/iiii-project/tree/main/opik/.agents/skills/debugging-e2e-tests
Command: npx skills add https://github.com/jimmy071919/iiii-project --skill debugging-e2e-tests

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the need for investigating failed Opik end-to-end tests, providing insights into the root cause of failures.

Core Features & Use Cases

Failure Analysis: Identifies whether a test failure is due to a regression, flake, or environmental issue.
Evidence Gathering: Collects traces, history, and other relevant information from local runs, CI checks, and TestOps launches.
Classification: Classifies the nature of the failure and proposes a fix.
Use Case: When a CI check fails, this skill can be used to determine the cause and suggest a potential fix.

Quick Start

Use the debugging-e2e-tests skill to investigate the failing run on my PR.

Frequently Asked Questions about debugging-e2e-tests

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

FAQPage Schema

How do I analyze failed Opik E2E tests in my CI pipeline?▼

To analyze failed Opik E2E tests, this skill gathers evidence from CI checks, local runs, and TestOps launches, classifies the failure as a regression, flake, or environmental issue, and proposes a targeted fix.

What is the best way to investigate Opik test failures from a pull request?▼

The best way to investigate Opik test failures from a pull request is to trigger this skill, which automatically collects traces and history from your failing run to classify the root cause and suggest a potential fix.

Can I classify E2E test failures from local runs and TestOps launches?▼

Yes, you can classify E2E test failures from local runs and TestOps launches; the skill evaluates gathered evidence to determine whether the failure stems from a regression, a flake, or an environmental issue.

Do I need GitHub access to debug Opik E2E test failures?▼

Yes, you need access to GitHub, TestOps, and the Opik test environment to fully gather evidence, investigate failing runs, and propose accurate fixes for your E2E test failures.

Why does my Opik E2E test check keep failing in CI?▼

Your Opik E2E test check might be failing due to a regression, a flake, or an environmental issue; this skill collects traces and run history to pinpoint the exact cause and propose a resolution.

Are there limitations when investigating Opik end-to-end test failures?▼

Investigating Opik end-to-end test failures requires access to GitHub, TestOps, and the Opik test environment; without these integrations, the skill cannot gather the necessary evidence or propose accurate fixes.