samgalanakis/skills · Archived

ghmonitor

Monitor GitHub Actions workflow runs using gh CLI. Polls for progress, reports status at regular intervals until completion or failure. On failure, diagnoses the issue and fixes it.

First seen Apr 13, 2026

Installation

$ npx skills add samgalanakis/skills --skill ghmonitor

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from samgalanakis/skills.

npx skills add samgalanakis/skills

Browse all from samgalanakis/skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 1
Default branch main
Open issues 0
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,222 B
  • docs SUMMARY.md 198 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

GH Monitor

Monitor GitHub Actions runs and fix failures automatically.

Workflow

  1. Find the most recent run for the current branch:

``bash gh run list --branch "$(git branch --show-current)" --limit 1 --json databaseId,status,conclusion,name,createdAt ``

  1. Poll with gh run view <id> --json status,conclusion,jobs,name,createdAt,updatedAt
  2. Report concise status each poll:

`` [2m 30s] deploy — build (running), test (queued), deploy (queued) [5m 15s] deploy — All jobs completed (5m 15s) ``

  1. On success — report final duration
  2. On failure — diagnose and fix (see below)

Polling

Every 10 seconds. After 10 minutes, slow to every 30 seconds. Use background task tools, not sleep loops.

Failure Handling

  1. Get logs: gh run view <id> --log-failed
  2. Diagnose root cause
  3. Fix code/config, commit, push
  4. Automatically monitor the new triggered run — don't ask, just do it
  5. Give up after 3 fix attempts — report status and ask the user