github-actions-ci

Monitor GitHub Actions workflow runs, retrieve failure logs, and trigger workflows via gh CLI.

Updated Mar 5, 2026
One-click install
npx skills add https://github.com/faccomichele/open-claw-team --skill github-actions-ci-faccomichele
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-actions-ci
Source: https://github.com/faccomichele/open-claw-team/tree/main/skills/github-actions-ci
Command: npx skills add https://github.com/faccomichele/open-claw-team --skill github-actions-ci-faccomichele

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the tedious manual work of tracking GitHub Actions CI pipeline status, sifting through run logs, and manually triggering workflows, saving development, QA, and operations teams hours of repetitive effort.

Core Features & Use Cases

  • Workflow Status Monitoring: List recent workflow runs, view detailed run and job status, and watch running workflows in real time.
  • Failure Debugging: Retrieve full logs for failed runs to quickly identify root causes of CI failures.
  • On-Demand Workflow Management: Trigger workflows manually and track Actions usage for cost reporting.
  • Use Case: A QA agent can automatically check CI status when reviewing a PR, pull failure logs to analyze issues, and post a summary directly to the PR. A cost controller can pull Actions usage metrics to include in monthly budget reports.

Quick Start

Use the github-actions-ci skill to check the latest CI run status for the open-claw-team repository and retrieve logs for any failed runs.

Frequently Asked Questions about github-actions-ci

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

FAQPage Schema
How do I check GitHub Actions workflow status from the command line?

You can check GitHub Actions workflow status by listing recent runs and viewing detailed job statuses. This skill monitors running workflows in real time to eliminate manual tracking overhead.

How do I retrieve logs for failed GitHub Actions runs?

Retrieve logs for failed GitHub Actions runs by pulling the full failure logs directly through the GitHub API. This quickly identifies root causes of CI failures without manual sifting.

Do I need the gh CLI to trigger GitHub Actions workflows manually?

Yes, you need the gh CLI binary and a valid GITHUB_TOKEN environment variable to trigger GitHub Actions workflows manually. These prerequisites allow interaction with the GitHub API for all CI operations.

Can I track GitHub Actions usage for budget reporting?

You can track GitHub Actions usage for budget reporting by pulling Actions usage metrics. This allows cost controllers to include CI consumption data directly in monthly budget reports.

What is the best way to debug CI pipeline failures in GitHub Actions?

The best way to debug GitHub Actions CI pipeline failures is retrieving full logs for failed runs to quickly identify root causes. This automates failure analysis for development and QA teams.

Can a QA agent automatically post GitHub Actions CI summaries to a pull request?

A QA agent can automatically check CI status when reviewing a PR, pull failure logs to analyze issues, and post a summary directly to the PR. This automates PR review workflows.