view-run

View and summarize CI workflow runs from GitHub Actions or Gitea.

6|3|Updated Sep 13, 2017
One-click install
npx skills add https://github.com/tomholford/dotfiles --skill view-run
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: view-run
Source: https://github.com/tomholford/dotfiles/tree/main/claude/skills/view-run
Command: npx skills add https://github.com/tomholford/dotfiles --skill view-run

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

View and summarize CI workflow runs from GitHub Actions or Gitea in a single, consistent view, reducing time spent checking statuses across platforms.

Core Features & Use Cases

  • View the most recent run for the current branch or a specific run by ID, URL, PR number, or branch.
  • Get a concise summary including status, branch, triggering commit/PR, duration, and relevant logs for failed steps.
  • Works with GitHub Actions and Gitea-compatible runners by selecting the appropriate CLI path automatically.

Quick Start

View the latest run for the current branch or specify a run by ID, URL, PR, or branch.

Frequently Asked Questions about view-run

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

FAQPage Schema
How do I check the status of a GitHub Actions or Gitea CI run?

To check CI run status, the tool fetches workflow runs from GitHub Actions using gh or Gitea using mcp adapters, returning a concise summary of the build status, triggering commit, duration, and failed step logs.

Can I view CI workflow runs for a specific pull request or branch?

Yes, you can view CI workflow runs for a specific pull request or branch by passing the PR number or branch name, or fetch the most recent run for the current branch with no arguments.

What's the best way to summarize CI run results across multiple platforms?

Summarizing CI run results across platforms is done by automatically selecting the appropriate CLI path for GitHub or Gitea, presenting a unified status summary including duration and relevant logs for failed steps.

Does this work with both GitHub Actions and Gitea runners?

It works with both GitHub Actions and Gitea-compatible runners, automatically selecting the appropriate adapter or CLI tool to fetch and present the workflow run data consistently.

Can I look up a specific CI run by URL or run ID?

Looking up a specific CI run by URL or run ID is supported, allowing you to target an exact workflow execution and retrieve its status, branch, triggering PR, and failure logs.

Why do I need to check CI runs from the command line instead of the web UI?

Checking CI runs from the command line reduces time spent navigating web interfaces across platforms, providing a consistent, concise summary of status, duration, and failed step logs in one view.