Diagnose CI UI test failures by collecting logs and classifying errors.
npx skills add https://github.com/o3-ozono/atdd-kit --skill ui-test-debugging
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
Diagnose CI UI Test failures in PR workflows by collecting logs, classifying errors, reproducing locally, and delivering a structured diagnostic report.
Trigger a diagnostic session by describing the failing PR's CI UI tests and providing access to relevant logs.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
benzwickDownload GitHub Actions CI artifacts using gh CLI commands.
petekpDiagnose stuck agent-assisted development and propose verifiable fixes.
naruseniaPost PR review findings as GitHub inline comments.
openshift-engAnalyze Prow CI job artifacts to classify test failures versus infrastructure flakes.
