ci-monitoring

Monitors GitHub PR CI checks, resolves failures and review feedback, then merges.

Updated Jan 1, 2026
One-click install
npx skills add https://github.com/sarkarshivaditya-lab/WellMate --skill ci-monitoring-sarkarshivaditya-lab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ci-monitoring
Source: https://github.com/sarkarshivaditya-lab/WellMate/tree/main/.engineering-skills/troykelly-claude-skills/skills/ci-monitoring
Command: npx skills add https://github.com/sarkarshivaditya-lab/WellMate --skill ci-monitoring-sarkarshivaditya-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? After opening a pull request, developers must repeatedly poll CI status, diagnose failing checks, respond to review comments, and remember to merge—an error-prone manual loop that stalls delivery. ## Core Features & Use Cases - CI Failure Diagnosis: Identifies failing checks with gh pr checks and gh run view --log-failed, then guides reproduction and fixes for test, build, lint, typecheck, and flaky-test failures. - Review Thread Resolution: Queries unresolved review threads via the GitHub GraphQL API, evaluates each comment, replies in-thread, and resolves or defers feedback with tracking issues. - Gated Auto-Merge: Merges with gh pr merge --squash --delete-branch only when CI is green and no unresolved threads remain, respecting do-not-merge labels. - Use Case: After creating a PR for a bug fix, let the assistant watch the pipeline, fix a lint failure, reply to a CodeRabbit security comment, resolve the thread, and squash-merge once everything passes. ## Quick Start Monitor the CI checks and review feedback on my open pull request, fix any failures, and merge it when everything passes.

Frequently Asked Questions about ci-monitoring

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I monitor GitHub PR checks from the command line?▼

Use `gh pr checks [PR_NUMBER]` to see current check status, or add `--watch` to poll until checks complete. For failures, run `gh run view [RUN_ID] --log-failed` to inspect the failing job logs.

How to find unresolved review threads on a GitHub pull request?▼

Query the GitHub GraphQL API for `reviewThreads` on the pull request and filter nodes where `isResolved` is false. Each thread includes the first comment's body, author, and file path for evaluation.

Can I resolve a GitHub review thread with the gh CLI?▼

Yes, call the GraphQL `resolveReviewThread` mutation via `gh api graphql` with the thread ID. Reply in the thread first using the pulls comments replies endpoint so reviewers see your response before resolution.

Why does my test pass locally but fail in CI?▼

This indicates a flaky test caused by race conditions, environment differences, or state pollution between tests. Replace fixed delays with condition-based waits and ensure tests are isolated from shared state.

When should I not merge a pull request automatically?▼

Do not merge when the PR has a `do-not-merge` label, when CI failures are caused by your code, or when review threads remain unresolved. Document external CI infrastructure issues in a PR comment instead of merging through them.