ci-watch
Skill0 starsChanged 8 months agoMITView on GitHub
Check GitHub Actions CI status for the current branch. Reports pass/fail/in-progress. Designed to be used standalone or with /loop: "/loop 2m ci-watch". Triggers: "check CI", "watch build", "is CI passing", "CI status", after any git push.
- Commits and pushes
4 other projects use a version of this.
Adopted by
Most recently taken up by
- jisuzzzz/haechitheir own version, first seen Nov 8, 2026
- cill-i-am/skillstheir own version, first seen Oct 20, 2026
- nubjs/nubtheir own version, first seen Oct 8, 2026
- nfeuer/project-foundation-kittheir own version, first seen Jul 5, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- nubjs/nub★ 4.4ksame name
- jisuzzzz/haechi★ 17same name
- cill-i-am/skills★ 1same name
- nfeuer/project-foundation-kit★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository20 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- commitSkill
- discovery-interview-prepSkill
- doc-generateSkill
- incident-responseSkill
- opportunity-solution-treeSkill
- polarisSkill
- prd-developmentSkill
- prioritization-advisorSkill
- reviewSkill
- roadmapSkill
- security-auditSkill
- session-wrapSkill
- spec-updateSkill
- tddSkill
- tech-debt-auditSkill
- test-runnerSkill
- user-storySkill
- uxSkill
- workshop-facilitationSkill
The file
Files
CI Watch — GitHub Actions Status Check
Purpose
Single-purpose skill: check the current CI run status and report it clearly.
Designed to be called once (standalone) or on a loop (/loop 2m ci-watch) after a git push.
Application
Step 1 — Get current branch
git branch --show-currentStep 2 — Fetch CI run status
gh run list --limit 1 --json status,conclusion,name,headBranch,createdAt,urlStep 3 — Interpret and report
| status | conclusion | Report |
completed | success | CI GREEN — all checks passed. |
completed | failure | CI RED — run failed. Show URL + failing step. |
completed | cancelled | CI CANCELLED — run was cancelled. |
in_progress | — | CI IN PROGRESS — still running. |
queued | — | CI QUEUED — waiting for runner. |
For failures, also run:
gh run view --log-failedto show the specific failing step.
Step 4 — Advise
- Green: "CI passed. Safe to continue."
- Red: "CI failed on [step]. Fix before moving on. Run
gh run view --log-failedfor details." - In progress: "Still running. Run
/ci-watchagain in ~1 min, or use/loop 2m ci-watch."
Loop Integration
To monitor continuously after a push:
/loop 2m ci-watchThe loop auto-stops when you cancel it (Ctrl+C). Suggest stopping once CI reaches a terminal state (success or failure).
Common Pitfalls
Pitfall 1: No runs found
Symptom: gh run list returns empty.
Fix: The push may not have triggered CI (no workflow file, or push to a branch with no triggers). Check .github/workflows/.
Pitfall 2: Multiple concurrent runs
Symptom: --limit 1 returns a run from a different branch.
Fix: Filter by branch: gh run list --limit 1 --branch $(git branch --show-current)
References
- Related skill:
/commit— suggests/ci-watchin step 9e post-push - Related rule:
workflow.md— Loop & Monitoring section - Agent:
ci-monitor— haiku agent that executes the gh CLI calls above
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.