gh-workflows

Inspect, trigger, and cancel GitHub Actions workflows from the terminal.

1|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/jieni777/opencode-config-backup --skill gh-workflows-jieni777
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-workflows
Source: https://github.com/jieni777/opencode-config-backup/tree/main/skills/gh-workflows
Command: npx skills add https://github.com/jieni777/opencode-config-backup --skill gh-workflows-jieni777

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GitHub Actions management from the terminal: inspect, trigger, and monitor workflows from a single shell.

Core Features & Use Cases

  • List workflows in a repository: view ids, names, and paths to plan automation tasks.
  • Trigger runs programmatically: start a workflow with a specific ref or branch and monitor progress.
  • Monitor, view, and cancel runs: fetch run details, watch for status changes, and cancel in_progress runs when needed.
  • Use Case: A devops engineer quickly audits CI pipelines across multiple repos and reruns failed jobs without leaving the CLI.

Quick Start

Trigger a workflow with gh workflow run using the specified workflow name and branch.

Frequently Asked Questions about gh-workflows

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

FAQPage Schema
How do I trigger and monitor GitHub Actions workflows from the terminal?

You can trigger and monitor GitHub Actions workflows from the terminal by running CLI commands to start runs on specific branches and fetching run details to watch for status changes. This allows managing CI pipelines without leaving the shell.

Can I cancel in-progress GitHub Actions runs via the command line?

Yes, you can cancel in-progress GitHub Actions runs via the command line. The functionality fetches active run details and executes cancellation commands to stop ongoing workflows across authenticated repositories when needed.

Do I need jq and gh CLI to manage GitHub Actions workflows in the terminal?

Yes, you need jq and gh CLI to manage GitHub Actions workflows in the terminal. The gh CLI requires repo and workflow scopes for authentication, while jq is used for formatting workflow and run data fetched from GitHub.

What environment variables are required to list and trigger GitHub Actions workflows?

To list and trigger GitHub Actions workflows, the environment variables required include GITHUB_REPOSITORY and DEFAULT_BRANCH. These variables resolve target repositories and branches to correctly scope workflow automation commands.

What is the best way to audit CI pipelines across multiple repositories without a browser?

The best way to audit CI pipelines across multiple repositories without a browser is using terminal commands to list workflow ids, names, and paths. This enables DevOps engineers to quickly inspect and rerun failed jobs directly from the CLI.