skills.rest
BillAnastasiadis
BillAnastasiadisCOMMUNITY
Explore all skills by this author →
GitHub

openQA Review Assistant

Analyze openQA test failures by fetching job data and tracing code.

Updated May 11, 2026
Search Tags:#code tracing#test failure analysis#QA engineering#historical data analysis#openQA
One-click install
npx skills add https://github.com/BillAnastasiadis/openqa-review-assist-gemini --skill openqa-review-assistant
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openQA Review Assistant
Source: https://github.com/BillAnastasiadis/openqa-review-assist-gemini/tree/main/.gemini/skills/openqa-triage
Command: npx skills add https://github.com/BillAnastasiadis/openqa-review-assist-gemini --skill openqa-review-assistant

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides a comprehensive analysis of openQA test failures, offering detailed insights into the root cause of failures by leveraging historical data and code analysis.

Core Features & Use Cases

  • Test Failure Analysis: In-depth analysis of openQA test failures.
  • Code Tracing: Detailed code tracing to understand the root cause of errors.
  • Historical Data Analysis: Analyze historical job data to identify patterns and regressions.
  • Use Case: When a user reports a test failure in openQA, this Skill can be used to diagnose the issue by analyzing the code, comparing commits, and checking historical data.

Quick Start

Use the openQA Review Assistant skill to review an openQA job: /review 1234567

Frequently Asked Questions about openQA Review Assistant

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

FAQPage Schema
How do I analyze openQA test failures to find the root cause?▼

Analyzing openQA test failures involves fetching job data, tracing code, comparing commits, and cross-referencing historical records. This comprehensive analysis identifies patterns and regressions to pinpoint the exact root cause of the test failure.

How do I trace code to understand why an openQA job failed?▼

Tracing code for an openQA job requires fetching specific job data and using Python scripts for extraction. The analysis traces execution paths against historical records to understand why the test failure occurred.

Do I need Python to perform historical data analysis on openQA jobs?▼

Yes, Python is required as a dependency to perform historical data analysis on openQA jobs. Python scripts are utilized for data extraction and analysis to identify patterns and regressions within the historical records.

Can I use code tracing to diagnose openQA regressions by comparing commits?▼

Yes, you can diagnose openQA regressions by comparing commits and tracing code. Cross-referencing historical job data alongside commit comparisons reveals patterns that indicate whether a recent change caused the failure.

What are the limitations when analyzing openQA test failures with scripts?▼

When analyzing openQA test failures with scripts, operations must occur within strict security and execution constraints. These limitations ensure the analysis does not compromise the environment during data extraction and code tracing.

Related Skills

Explore More Software Engineering Skills→
dwertentdwertent

ci-fix

Diagnose GitHub Actions CI failures from run URLs and propose fixes.

Community
Intermediate
derekcrossluderekcrosslu
2

Backtesting Analysis

Interpret backtest results and detect overfitting in trading strategies.

Community
Basic
santosomarsantosomar
1

szz-bug-identifier

Apply the SZZ algorithm to Git history to identify bug-introducing commits.

Community
Intermediate
SonarSourceSonarSource
1.3k

peach-check

Analyze and classify Peach Main Analysis failures for SonarJS releases.

Official
Intermediate