Monitor GitHub Actions CI status and retrieve failed run logs.
npx skills add https://github.com/dbmrq/Dotfiles --skill ci-watcher
Please help me install this Agent Skill. Skill: ci-watcher Source: https://github.com/dbmrq/Dotfiles/tree/main/Augment/.augment/skills/ci-watcher Command: npx skills add https://github.com/dbmrq/Dotfiles --skill ci-watcher
This Skill automates monitoring of GitHub Actions CI status after pushing changes to a repository that contains a .github/workflows directory, providing proactive visibility into builds and failures.
Ensure GitHub CLI (gh) is installed and you are in a git repository on the target branch. Run: bash scripts/check_ci.sh --wait 300 To view the latest run details or logs, use: gh run list --branch $(git branch --show-current) --limit 1 gh run view <run-id> --log-failed
High-intent search queries and answers about installing and using this skill.
To monitor GitHub Actions CI status automatically after a push, you can use a script that polls the latest workflow run in your repository and reports the results. This allows you to track build progress and identify failures without manually checking the GitHub UI.
To get logs for failed GitHub Actions workflow runs, you can query the specific run ID and retrieve the failed logs. This provides actionable insights into which steps failed, directly aiding your debugging process from the terminal.
Yes, you need the GitHub CLI (gh) installed to check CI status and workflow logs locally. The monitoring process queries workflow runs and retrieves logs using the gh CLI, alongside the bundled check_ci.sh script.
No, this CI monitoring tool applies specifically to software projects using GitHub Actions. It targets repositories containing a .github/workflows directory to monitor workflow runs and report status updates after pushes.
The best way to automatically check GitHub Actions build results without leaving the terminal is running a polling script like check_ci.sh. It continuously observes the latest workflow run, reports health status, and highlights failing steps for quick debugging.
Your GitHub Actions CI monitoring script returns no workflow runs if the repository lacks a .github/workflows directory or the gh CLI is not properly authenticated. It requires both to query and present the latest CI status for your current branch.
kagentiAggregate Git worktree status, pull request details, and TODO file summaries.
akiojinDiagnose failing GitHub Actions checks on pull requests and generate fix plans.
doanchienthangdevImplements Git hooks to automate pre-commit checks, commit validation, and pre-push tests.
robbytManage GitHub Actions workflows and inspect runs via the gh CLI.
