ui-test-debugging

Diagnose CI UI test failures by collecting logs and classifying errors.

Updated Aug 23, 2026

Search Tags:#debugging #diagnostics #log-analysis #pr-review #ui-test #ci-failure #xcuitest

Ready to run

npx skills add https://github.com/o3-ozono/atdd-kit --skill ui-test-debugging

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ui-test-debugging
Source: https://github.com/o3-ozono/atdd-kit/tree/main/skills/ui-test-debugging
Command: npx skills add https://github.com/o3-ozono/atdd-kit --skill ui-test-debugging

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnose CI UI Test failures in PR workflows by collecting logs, classifying errors, reproducing locally, and delivering a structured diagnostic report.

Core Features & Use Cases

Diagnose CI UI test failures across PR workflows (XCUITest, XCTest UI) by retrieving CI logs, identifying root causes, and guiding remediation.
Provide evidence-rich diagnostics including failure messages, step traces, and reproducibility steps for engineers and reviewers.
Support PR-comment style reporting and handoff to the ATDD workflow for fixes and verification.

Quick Start

Trigger a diagnostic session by describing the failing PR's CI UI tests and providing access to relevant logs.

Frequently Asked Questions about ui-test-debugging

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

FAQPage Schema

How do I diagnose CI UI test failures in a PR workflow?▼

Diagnosing CI UI test failures involves collecting CI logs, classifying errors as CI-specific or code-related, optionally reproducing locally, and generating a structured diagnostic report for PR review.

What is the best way to classify XCUITest failures from CI logs?▼

Classifying XCUITest failures involves analyzing retrieved CI logs to distinguish CI-specific errors from code-related issues, then documenting failure messages and step traces for remediation guidance.

Does this diagnostic process support local reproduction of XCTest UI errors?▼

Yes, the diagnostic process supports optional local reproduction steps for XCTest UI errors, collecting evidence such as failure messages and step traces to help engineers verify fixes.

Can I use gh run view to collect logs for PR UI test diagnostics?▼

Yes, you can use gh run view to retrieve CI logs, which are then analyzed to identify root causes of UI test failures and generate a structured diagnostic report for PR comments.

When do I need a structured diagnostic report for UI test failures?▼

A structured diagnostic report is needed when handing off UI test failure findings to engineers and reviewers, providing evidence-rich diagnostics including failure messages, step traces, and reproducibility steps.