ci-pr-monitor
Skill3 starsChanged 4 days agoMITView on GitHub
Repeatable workflow for monitoring CI check status, tracking PR merge-readiness, and verifying auto-merge success using the gh CLI.
In this repository153 other files it gives its agents.
- AGENTS.mdAGENTS.md
- hermes-mobile/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/agent-automations.mdcCursor rule
- .cursor/rules/agent-device.mdcCursor rule
- .cursor/rules/agent-harness-router.mdcCursor rule
- .cursor/rules/agent-skills-overview.mdcCursor rule
- .cursor/rules/always-agent-mode.mdcCursor rule
- .cursor/rules/callstack-agent-skills-overview.mdcCursor rule
- .cursor/rules/callstack-react-native-best-practices.mdcCursor rule
- .cursor/rules/codeql-agent-hygiene.mdcCursor rule
- .cursor/rules/decision-stack.mdcCursor rule
- .cursor/rules/expo-credit-budget.mdcCursor rule
- .cursor/rules/fleet-repo-intelligence.mdcCursor rule
- .cursor/rules/hermes-mobile-prevention-july-2026.mdcCursor rule
- .cursor/rules/hermes-mobile-real-users.mdcCursor rule
- .cursor/rules/hermes-mobile-verification.mdcCursor rule
- .cursor/rules/no-desktop-hijack.mdcCursor rule
- .cursor/rules/no-manual-handoffs.mdcCursor rule
- .cursor/rules/obsidian-teammate-collaboration.mdcCursor rule
- .cursor/rules/prefer-headless-background-ops.mdcCursor rule
- .cursor/rules/react-native-best-practices.mdcCursor rule
- public/llms.txtllms.txt
- advertise-thumbgate-github-marketplaceSkill
- agent-harness-routerSkill
- agentic-pattern-selectorSkill
- agents-judgment-calls-gateSkill
- ai-native-sdlcSkill
- android-dev-summit-26-gateSkill
- anti-babysitting-mandateSkill
- anti-babysittingSkill
- background-agent-hold-gateSkill
- browseros-agent-harnessSkill
- webmcp-agent-readinessSkill
- ci-first-failSkill
- cloudflare-developer-stackSkill
- cloudflare-kitesurf-browserSkill
- cloudflare-monetization-gatewaySkill
- confidence-offer-gateSkill
- content-laneSkill
- context-six-blockSkill
- context-vaultSkill
- context-weight-gateSkill
- dual-model-agentic-graphragSkill
- egm-fresh-reviewSkill
- elevenlabs-voice-agentsSkill
- emeans-quant-and-instinctSkill
- explainx-trending-honestSkill
- explainx-trending-ragSkill
- future-agi-self-healing-engineSkill
- garryslist-opportunity-trackerSkill
- gemini-decisions-hold-gateSkill
- git-at-scaleSkill
- gitbutler-fleet-automationsSkill
- gitbutler-google-ssoSkill
- gitbutler-mcp-isolatedSkill
- gitbutler-session-absorbSkill
- git-hooks-no-huskySkill
- github-marketplace-action-publishSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 20
Use this skill whenever you need to verify GitHub Actions CI check status, track PR merge-readiness, or confirm auto-merge success.
- Very specific: line 45
Auto-merge: If mergeable: MERGEABLE and mergeStateStatus: CLEAN, run gh pr merge <PR> --auto --squash.
- Very specific: line 52
If state: "MERGED", the PR is already in main.
- Very specific: line 56
Never gh run rerun a queued run — it's a no-op.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
CI-PR Monitor Skill
Use this skill whenever you need to verify GitHub Actions CI check status, track PR merge-readiness, or confirm auto-merge success.
Quick Commands
| Action | Command |
| List all checks for a PR | gh pr checks <PR_NUM> |
| JSON status of a PR | gh pr view <PR_NUM> --json state,mergeable,mergeStateStatus |
| Get required status contexts | gh api repos/<owner>/<repo>/branches/<branch>/protection --jq '.required_status_checks.contexts[]' |
| Enable auto-merge (squash) | gh pr merge <PR_NUM> --auto --squash |
| Wait for a specific check | gh pr checks <PR_NUM> --watch |
| Get workflow runs for a branch | gh api repos/<owner>/<repo>/actions/workflows/<workflow>/runs --jq '[.workflow_runs[] | select(.head_branch=="<branch>")]' |
Decision Flow
- Check current status:
gh pr checks <PR> --json name,state,conclusion - Classify results:
pass/SUCCESS→ check is greenpending→ still running, waitfail/FAILURE→ investigate the failing stepskipping→ not applicable to this change
- Required checks only: Compare against the protected-branch required contexts. Non-required checks (e.g., macOS runners, mobile E2E) that remain pending should NOT block merge if all required checks are green.
- Auto-merge: If
mergeable: MERGEABLEandmergeStateStatus: CLEAN, rungh pr merge <PR> --auto --squash. GitHub will queue the merge for when all required checks clear.
Notes
- The
mergeStateStatusfield returnsUNKNOWNonce the PR is merged. Ifstate: "MERGED", the PR is already inmain. - Cloudflare/GitHub Actions queue storms: check GitHub Status API (https://www.githubstatus.com/api/v2/summary.json) before blaming code or runners if checks are missing (not failing).
- Never
gh run reruna queued run — it's a no-op. - Auto-merge via
--autorequires thepull-requests: writepermission.
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.

