github-workflows

Diagnose GitHub Actions workflow failures and validate CI/CD configurations.

1|Updated Jul 13, 2026
One-click install
npx skills add https://github.com/vh2224/forge-executor --skill github-workflows-vh2224
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-workflows
Source: https://github.com/vh2224/forge-executor/tree/main/src/resources/skills/github-workflows
Command: npx skills add https://github.com/vh2224/forge-executor --skill github-workflows-vh2224

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires typer>=0.21.0, PyGithub>=2.1.1, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps you work with GitHub Actions without relying on stale workflow syntax or guesswork, so you can create, inspect, and debug CI/CD pipelines using current documentation and observable run output.

Core Features & Use Cases

  • Workflow authoring: Uses live GitHub Actions reference docs to write correct workflow syntax, triggers, permissions, concurrency, and reusable workflows.
  • Run monitoring and debugging: Routes CI checks through ci_monitor.cjs to list runs, watch executions, inspect failed logs, and summarize test results.
  • Version and configuration validation: Checks action versions and validates observable changes so workflow edits are proven rather than assumed.

Quick Start

Ask the skill to review your GitHub Actions workflow, verify it against the current docs, and debug the latest failing run using the repository’s monitoring script.

Frequently Asked Questions about github-workflows

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

FAQPage Schema
How do I debug GitHub Actions workflow failures using live run data?

Debug GitHub Actions workflow failures by routing CI checks through the ci_monitor.cjs observation script to list runs, watch executions, inspect failed logs, and summarize test results for accurate failure analysis.

How do I validate GitHub Actions CI/CD configurations against current documentation?

Validate CI/CD configurations by checking action versions and observable changes against live GitHub Actions reference docs for syntax, triggers, permissions, concurrency, and reusable workflows to ensure edits are proven rather than assumed.

What is the best way to author GitHub Actions workflows without relying on stale syntax?

Author GitHub Actions workflows using live reference documents for correct syntax, contexts, expressions, and event behavior, ensuring triggers, permissions, and reusable workflows are validated against current documentation rather than guesswork.

Does this GitHub Actions debugging approach require the GitHub CLI to monitor workflow runs?

Monitoring workflow runs requires the ci_monitor.cjs script for observation, alongside PyGithub for API access, to list runs, watch executions, and inspect failed logs within GitHub repositories.

Can I use this to inspect failed logs and summarize test results for GitHub Actions runs?

Yes, you can inspect failed logs and summarize test results by routing CI checks through the ci_monitor.cjs workflow observation script, which lists runs and watches executions to diagnose failures using current run data.

Why do my GitHub Actions workflow edits fail despite syntax validation?

Workflow edits fail when assumed rather than proven, so validating observable changes and action versions against live GitHub Actions reference documentation for syntax, contexts, and event behavior is necessary to prevent failures.