dyad:check-workflows

Audits recent GitHub Actions workflow runs and files issues for actionable failures.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually reviewing dozens of daily GitHub Actions runs to distinguish real problems from expected noise is tedious and error-prone. This Skill automates that triage, classifying failures as expected or actionable and filing a GitHub issue only when genuine problems exist.

Core Features & Use Cases

  • Failure Classification: Applies explicit rules to ignore expected failures (Nightly Runner Cleanup, cascading CI failures, CLA Assistant, cancelled runs) and flag actionable ones (permission errors, main-branch CI breakage, infrastructure issues).
  • Severity Assessment: Investigates failed runs via gh run view logs and categorizes findings as SEVERE, MODERATE, or LOW.
  • Deduplicated Issue Filing: Checks for existing open workflow-health issues before creating a new one, adding comments instead of duplicates.
  • Use Case: Run a daily health check on the dyad repository to catch a broken CI pipeline on main or a misconfigured secret before it blocks all contributors.

Quick Start

Ask the assistant to check GitHub Actions workflow runs from the past 24 hours and file an issue if any actionable failures are found.

Frequently Asked Questions about dyad:check-workflows

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

FAQPage Schema
How do I check GitHub Actions workflow runs for failures?

Use `gh run list --limit 100 --json workflowName,status,conclusion,createdAt` to fetch recent runs, then filter by your lookback window and group by workflow name. This Skill automates that process and classifies each failure as expected or actionable.

How to distinguish real CI failures from expected workflow noise?

Expected failures include cascading failures from a broken main CI, CLA Assistant checks, concurrency-cancelled runs, and fork PR approvals. Actionable failures include permission errors, repeated main-branch CI breakage, infrastructure outages, and workflow configuration errors.

Can I change the time window for the workflow health check?

Yes, pass an optional argument specifying the number of hours to look back. The default window is 24 hours, and only runs created within that window are analyzed.

Does this create duplicate GitHub issues for the same workflow problem?

No. Before filing, it runs `gh issue list --label workflow-health --state open` to find existing issues. If a matching issue exists, it adds a comment with the latest findings instead of creating a duplicate.

Why are some failed workflow runs ignored by the health check?

Runs like Nightly Runner Cleanup intentionally kill runner processes and always appear failed, while Playwright Report Comment and Flakiness.io uploads fail only as downstream effects of CI. Ignoring them prevents false alarms and focuses attention on real problems.