skills.rest
DengNaichen
DengNaichenCOMMUNITY
Explore all skills by this author →
GitHub

axiom-debug-tests

Analyze xcresult bundles and crash logs to diagnose failing iOS UI tests.

34|2|Updated Mar 16, 2026
Search Tags:#automation#testing#debugging#ios#xcode#ui-tests
One-click install
npx skills add https://github.com/DengNaichen/Stet --skill axiom-debug-tests
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: axiom-debug-tests
Source: https://github.com/DengNaichen/Stet/tree/main/.agents/skills/axiom-debug-tests
Command: npx skills add https://github.com/DengNaichen/Stet --skill axiom-debug-tests

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, xcodebuild, xcrun.

What problem does it solve?

This skill automates the tedious cycle of running, analyzing, and fixing failing UI tests, allowing developers to resolve test instability without manual intervention.

Core Features & Use Cases

  • Closed-Loop Debugging: Automatically captures failure logs, screenshots, and crash reports to identify root causes.
  • Pattern Recognition: Identifies common failure modes like missing accessibility identifiers, race conditions, or element visibility issues.
  • Use Case: When a UI test suite fails during CI, this skill can be triggered to analyze the failure, suggest a specific code fix, and verify the fix by re-running the test.

Quick Start

Use the axiom-debug-tests skill to analyze the latest test failure in the current project and suggest a fix.

Frequently Asked Questions about axiom-debug-tests

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

FAQPage Schema
How do I automate debugging for failing iOS UI tests during CI?▼

Automate failing iOS UI test debugging by analyzing xcresult bundles and crash logs to identify root causes, suggest specific code fixes, and verify the remediation by re-running the tests in a closed loop.

What is closed-loop debugging for Xcode UI test failures?▼

Closed-loop debugging for Xcode UI test failures automatically captures failure logs, screenshots, and crash reports, identifies common failure modes like missing accessibility identifiers or race conditions, and suggests targeted code fixes.

How do I analyze xcresult bundles to find the root cause of UI test crashes?▼

Analyze xcresult bundles to locate UI test crash root causes by parsing the bundle data with jq and utilizing xcodebuild command-line tools to extract diagnostic information and failure patterns.

Do I need jq and xcodebuild to automate iOS UI test failure analysis?▼

Yes, you need jq for JSON processing and xcodebuild command-line tools to parse xcresult bundles, alongside xcrun simulator control utilities to automate iOS UI test failure analysis and remediation workflows.

What's the best way to fix missing accessibility identifiers causing UI test failures?▼

The best way to fix missing accessibility identifiers causing UI test failures is using automated pattern recognition on failure logs to detect the specific missing elements and generate targeted code remediation suggestions.

Why does my automated UI test debugging not resolve race condition failures?▼

Automated UI test debugging might not resolve race condition failures if the crash logs lack sufficient timing data for pattern recognition, limiting the ability of the diagnostic workflow to suggest an effective remediation.

Related Skills

Explore More Software Engineering Skills→
n0ann0an
103

app-container

Print the iOS Simulator app container path for VivaDicta using xcrun and simctl.

Community
Basic
iPlug2iPlug2
152

run-ios-simulator

Build and launch iPlug2 iOS apps in the iOS Simulator with xcodebuild and xcrun simctl.

Official
Advanced
adamayoungadamayoung
1

test-ui

Execute UI test plans for Popcorn SwiftUI app on iOS simulators.

Community
Intermediate
s-iwasaki-bs-iwasaki-b

debug-run-ios

Build and install Compose Multiplatform iOS apps on simulators with xcodebuild.

Community
Advanced