Agent skill
monitoring-ci
Monitor and watch GitHub Actions CI/CD pipeline runs in real time. Use when the user has pushed code and wants to watch the build, check CI status, see if tests passed, monitor a pipeline, or wait for a workflow run to complete. Also use after any `jj git push` or `git push` command. Reports pass/fail with failed job logs. Do NOT use for writing or editing CI workflow YAML files, optimizing CI config, or debugging CI configuration — only for monitoring active runs.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/monitoring-ci
SKILL.md
CI Monitor
Watch GitHub Actions CI runs after a push. Auto-detects repo and branch, deduplicates concurrent monitors, reports results.
Usage
Run the script in the background after pushing:
uv run ~/.claude/skills/monitoring-ci/ci-monitor.py
With explicit branch:
uv run ~/.claude/skills/monitoring-ci/ci-monitor.py --branch my-feature
How to Invoke from Claude
After a push, run as a background Bash command:
uv run ~/.claude/skills/monitoring-ci/ci-monitor.py --branch <branch-name>
Use run_in_background: true so it doesn't block the conversation. Tell the user: "CI monitor running in background — you'll be notified when it completes."
Features
- Auto-detects branch: jj bookmarks first, falls back to git
- Deduplicates: sentinel file at
/tmp/{repo}-ci-monitorprevents double-watching - Polls for run: waits up to 60s for a CI run to appear on the branch
- Watches until done: uses
gh run watch --exit-status - Reports failure logs: on failure, fetches
gh run view --log-failed(last 3000 chars) - Cleans up: always removes sentinel, even on error
Exit Codes
0— CI passed (or no run found)1— CI failed (logs printed)
Requirements
ghCLI authenticated- GitHub Actions workflows in the repo
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?