github-actions-ci
// Check GitHub Actions CI status after pushing changes. Triggers after `git push` in projects with a `.github/workflows` directory. For Xcode Cloud builds (iOS/macOS projects without .github/workflows), use the xcode-cloud-ci skill instead.
$ git log --oneline --stat
stars:75
forks:14
updated:February 22, 2026
SKILL.mdreadonly
SKILL.md Frontmatter
namegithub-actions-ci
descriptionCheck GitHub Actions CI status after pushing changes. Triggers after `git push` in projects with a `.github/workflows` directory. For Xcode Cloud builds (iOS/macOS projects without .github/workflows), use the xcode-cloud-ci skill instead.
GitHub Actions CI Watcher
After performing a git push in a project with .github/workflows, check CI status.
Note: This skill is for GitHub Actions only. For Xcode Cloud builds, use the xcode-cloud-ci skill.
Workflow
- After pushing, wait before checking (CI needs time to start)
- Determine polling strategy based on project:
- Small projects / fast CI: wait 30-60s initially, poll every 15-30s
- Large projects / slow CI: wait 2-5min initially, poll every 30-60s
- Consider workflow file complexity, project size, and any prior knowledge
- Check status using the check_ci.sh script or
gh run list - On success: Report and continue
- On failure: Fetch logs, analyze the error, propose a fix, and ask user if they want it implemented
Checking Status
Use the bundled script:
scripts/check_ci.sh # Check once
scripts/check_ci.sh --wait 300 # Poll for up to 5 minutes
Or directly with gh CLI:
# List recent runs for current branch
gh run list --branch $(git branch --show-current) --limit 1
# View failed logs
gh run view <run-id> --log-failed
On Failure
- Fetch failure logs:
gh run view <run-id> --log-failed - Analyze the error and identify root cause
- Propose a specific fix with code changes
- Ask: "CI failed due to [reason]. I can fix this by [solution]. Should I implement this fix?"