gh-workflow

Trigger and monitor GitHub Actions workflows via gh CLI.

9|3|Updated Jun 29, 2012
One-click install
npx skills add https://github.com/whilp/dotfiles --skill gh-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-workflow
Source: https://github.com/whilp/dotfiles/tree/main/.claude/skills/gh-workflow
Command: npx skills add https://github.com/whilp/dotfiles --skill gh-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates running and tracking GitHub Actions workflows, ensuring proper push prerequisites and artifact retrieval.

Core Features & Use Cases

  • Workflow triggering: gh workflow run with inputs and refs.
  • Status tracking: list, watch, and download artifacts.
  • Remote validation: verify remote HEAD is pushed before triggering.

Quick Start

GH_HOST=github.com gh workflow run luajit.yml -f release_tag=2025.11.23

Frequently Asked Questions about gh-workflow

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

FAQPage Schema
How do I trigger GitHub Actions workflows from the command line?

Use gh workflow run to trigger workflows from the CLI. The Skill automates workflow triggering with input parameters and ref specifications, verifying that your local commits are pushed to the remote before execution begins.

Can I monitor GitHub Actions workflow status and download artifacts from the CLI?

Yes. The Skill tracks workflow runs using gh run list and gh run download to retrieve artifacts, enabling validation in CI/CD pipelines without leaving the terminal.

What checks does the Skill perform before triggering a workflow?

The Skill verifies that remotes exist and that your commits are pushed to the remote before triggering. It inspects workflow definitions in .github/workflows to understand triggers and required inputs.

Does this work with both workflow_dispatch and push-triggered workflows?

Yes. The Skill applies to both workflow_dispatch and push-triggered workflows, automatically validating prerequisites and handling input parameters appropriate to each trigger type.

Why would I use this instead of manually triggering workflows in the GitHub UI?

Automating workflow triggers and artifact retrieval from the CLI accelerates CI/CD pipelines and validation loops, eliminates manual steps, and integrates workflow management into your local development workflow.