debug-phoenix-hil-from-gha

Identify the primary cause of a Phoenix HIL failure in a GitHub Actions job run.

1|Updated Apr 15, 2024
One-click install
npx skills add https://github.com/yiminllin/dotfiles --skill debug-phoenix-hil-from-gha
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug-phoenix-hil-from-gha
Source: https://github.com/yiminllin/dotfiles/tree/main/opencode/.config/opencode/skills/debug-phoenix-hil-from-gha
Command: npx skills add https://github.com/yiminllin/dotfiles --skill debug-phoenix-hil-from-gha

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Phoenix HIL debugging in GitHub Actions often requires collecting scattered logs and artifacts to identify the root cause. This Skill orchestrates artifact retrieval, log analysis, and evidence-based reasoning to produce concise root-cause explanations with actionable fixes.

Core Features & Use Cases

  • Automatic resolution of a single job URL from a user-provided URL or descriptive input.
  • Aggregation and analysis of S3 logs, test records, validators, and internal summaries to surface the root cause.
  • Evidence-backed reporting with references to artifacts and code paths, plus suggested fixes.

Quick Start

Provide a GitHub Actions job URL or English description to analyze a single HIL job.

Frequently Asked Questions about debug-phoenix-hil-from-gha

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

FAQPage Schema
How do I debug Phoenix HIL failures in GitHub Actions?

To debug Phoenix HIL failures in GitHub Actions, provide a job run URL or English description. The Skill fetches S3 logs, test records, and validators to produce an evidence-backed root-cause analysis with recommended fixes.

What artifacts are needed to root-cause Phoenix HIL test failures?

Root-causing Phoenix HIL test failures requires S3 logs, test records, validators, and internal summaries. The Skill automatically gathers these artifacts from a GitHub Actions run to map failures to their source code paths.

Can I analyze a GitHub Actions job using an English description instead of a URL?

Yes, you can analyze a GitHub Actions job using an English description. The Skill resolves descriptive input to a single exact job run before fetching logs and artifacts for root-cause analysis.

Does this root-cause analysis approach work with scattered S3 logs and test records?

Yes, this root-cause analysis works with scattered S3 logs and test records. It aggregates and organizes artifacts from GitHub Actions to surface the primary cause of Phoenix HIL failures with file references.

How do I map HIL test failures to specific source code paths in GitHub Actions?

To map HIL test failures to source code paths, the Skill analyzes fetched artifacts and internal summaries. It documents findings with file references and code traces before concluding with actionable fixes.