dyad:pr-fix:ci

Diagnoses and fixes failing GitHub Actions CI checks on pull requests from run logs and artifacts.

21.4k|2.6k|Updated Apr 11, 2025
One-click install
npx skills add https://github.com/dyad-sh/dyad --skill dyad-pr-fix-ci
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dyad:pr-fix:ci
Source: https://github.com/dyad-sh/dyad/tree/main/.claude/skills/pr-fix-ci
Command: npx skills add https://github.com/dyad-sh/dyad --skill dyad-pr-fix-ci

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pull request CI failures in the dyad repository require manually digging through GitHub Actions logs, Playwright artifacts, and cross-platform test output to find root causes. This Skill automates that diagnosis and drives the fix through to publication.

Core Features & Use Cases

  • Run-Based Diagnosis: Locates the newest CI workflow run for the PR head SHA, enumerates failed jobs and steps, and reads the exact logs instead of guessing.
  • Cross-Platform Unit Test Analysis: Compares macOS and Windows unit-test job logs to distinguish shared failures from OS-specific ones, then reproduces the narrowest failing Vitest target locally.
  • E2E Failure Handling: Delegates Playwright shard failures to the deflake skill using html-report artifacts, reconstructs reports from blob-report artifacts when needed, and handles safe-storage-e2e and merge-reports job failures.
  • Use Case: A PR shows red CI with a Windows-only unit test failure and a failed E2E shard. The skill downloads both job logs, identifies the root causes, fixes the code, verifies with targeted tests plus fmt/lint/ts, and publishes via the pr-push skill.

Quick Start

Use the dyad:pr-fix:ci skill to diagnose and fix the failing CI checks on my current pull request.

Frequently Asked Questions about dyad:pr-fix:ci

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

FAQPage Schema
How do I fix failing CI checks on a GitHub pull request?

Identify the newest CI workflow run for the PR head SHA using gh run list, enumerate failed jobs and steps via the GitHub API, then diagnose each failure from its job log. Reproduce failures locally with the narrowest test command before fixing and republishing.

How to debug Playwright E2E failures from GitHub Actions artifacts?

Download the html-report artifact from the failed run and perform artifact-first trace analysis on the retained traces, screenshots, and error-context files. If only blob-report artifacts exist, download them all and run npx playwright merge-reports to reconstruct the HTML report locally.

Why does a unit test pass on macOS but fail on Windows CI?

Windows-only failures typically involve path separators, shell behavior, file locking, case sensitivity, or platform guards. Compare both job logs to confirm the failure is OS-specific, then add a platform-independent unit test and rely on the next Windows CI run for confirmation.

Can I run the safe-storage-e2e test locally on my Mac?

No. The safe-storage-e2e spec swaps the machine-global default macOS Keychain, so it must never run locally or on a self-hosted runner. Verify surrounding logic with narrow local tests and rely on the ephemeral GitHub-hosted job for final confirmation.

What commands verify fixes before publishing a CI fix?

Run the narrowest affected tests plus npm run fmt, npm run lint, and npm run ts. If E2E application code changed, run npm run build before targeted E2E tests, then publish with the pr-push skill.