pipeline-watch

Monitor CI/CD pipeline check statuses for pull requests on GitHub and Gitea.

3|1|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/jon23d/skillz --skill pipeline-watch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pipeline-watch
Source: https://github.com/jon23d/skillz/tree/main/skills/pipeline-watch
Command: npx skills add https://github.com/jon23d/skillz --skill pipeline-watch

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that Continuous Integration (CI) pipeline checks are successfully completed before a Pull Request (PR) is considered ready, preventing the merging of code with broken builds.

Core Features & Use Cases

  • CI/CD Monitoring: Automatically tracks the status of CI checks (tests, linting, builds) for opened PRs.
  • Status Reporting: Informs the user about the CI status, including success, failure, or timeouts.
  • Failure Handling: Provides guidance on how to address failing checks, such as rerunning jobs or delegating fixes.
  • Use Case: After a developer opens a PR, this Skill will monitor its CI pipeline, report back when all checks pass, or alert the team if a critical check fails.

Quick Start

Use the pipeline-watch skill to monitor the CI checks for the recently opened pull request.

Frequently Asked Questions about pipeline-watch

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

FAQPage Schema
How do I monitor CI/CD pipeline status for pull requests?

You can monitor CI/CD pipeline status for pull requests by using this Skill to track automated checks on newly opened PRs, executing commands like `gh pr checks` or polling the Gitea API to report success, failure, or timeouts.

What is the best way to prevent merging pull requests with broken CI builds?

Preventing merges of pull requests with broken CI builds requires pipeline monitoring that tracks check statuses and alerts the team if a critical check fails before the PR is deemed ready for review.

Does this CI monitoring work with both GitHub and Gitea repositories?

Yes, CI monitoring works with both GitHub and Gitea repositories, requiring delegation to agents with bash access to execute commands like `gh pr checks` for GitHub or interact with the Gitea API to poll commit statuses.

How do I handle failing CI checks detected on a pull request?

Handling failing CI checks detected on a pull request involves using the guidance provided by this Skill, such as rerunning jobs or delegating fixes to resolve the broken builds.

Do I need bash access to track automated quality gates for pull requests?

You need bash access to track automated quality gates for pull requests because this Skill requires delegating to agents to execute commands like `gh pr checks` or interact with the Gitea API.