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.
安装与使用
请根据来源仓库和你的 AI 工具说明安装此技能。先阅读技能文件和依赖要求,再添加到工作流。
查看来源 ↗使用指南技能说明
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?"
使用示例
查看来源仓库中的使用示例与配置说明。
查看来源 ↗来源历史
- 收录时间
- 2026-03-11
- 索引更新时间
- 2026-03-11
- Branch
- main
收录与同步日期属于本站记录。源码修改历史请查看来源仓库。
GitHub ↗chat Comments (0)
Sign in to join the discussion and leave a comment.
No comments yet. Be the first to share your thoughts!