Browse / Developer Tools / Check CI

Check CI

Monitors GitHub Pull Request status by polling CI checks until completion to automate development workflows.

SkillDeveloper ToolsVersion ControlProject ManagementIntegrationsOrchestrationGithub

The source repository doesn't declare a license. Check its terms before reusing the code.

Key features

  • Intelligent auto-detection of PR numbers from the current git branch
  • Seamless integration with GitHub CLI for authenticated repository access
  • Automated polling of GitHub PR status at configurable intervals
  • Real-time reporting of CI success, failure, and timeout states
  • Detailed failure analysis with suggestions for test, lint, and build fixes

Use cases

  • Verifying that a PR is green before merging or requesting a review
  • Automating CI checks as part of a post-push development workflow
  • Monitoring long-running build pipelines without manual intervention

FAQ

When should I use this skill?

Use this skill whenever you are waiting for tests to finish, verifying build health before a merge, or monitoring PR checks. It is ideal for queries like 'is my PR green?' or 'wait for CI to pass before proceeding.'

Does it require me to manually enter the PR number?

No, the skill features intelligent auto-detection. It can automatically identify the correct PR number based on your current active git branch, though you can provide a specific PR number if necessary.

What does the Check CI skill do?

The Check CI skill automates the monitoring of GitHub Pull Request statuses. It polls CI checks at configurable intervals and provides real-time updates on whether your build has passed, failed, or timed out.

What are the technical requirements to use Check CI?

To use this skill, you must be working within a git repository with an associated GitHub PR. Additionally, the GitHub CLI (gh) must be installed and authenticated on your local system.

How does it help when a CI check fails?

Beyond just reporting a failure, this skill performs detailed failure analysis. It identifies specific issues such as linting errors, test failures, or build crashes and suggests actionable fixes to help you resolve them quickly.