pr-watch

Monitor pull request CI status and apply targeted fixes to failing checks.

820|78|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/SethGammon/Citadel --skill pr-watch-sethgammon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-watch
Source: https://github.com/SethGammon/Citadel/tree/main/skills/pr-watch
Command: npx skills add https://github.com/SethGammon/Citadel --skill pr-watch-sethgammon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Monitors a pull request's CI status and automatically fixes failing checks by reading failure logs and applying targeted fixes, then optionally merges when all checks pass.

Core Features & Use Cases

  • Real-time CI status monitoring for a PR
  • Automatic, minimal fixes with optional auto-merge when green
  • Local CLI integration to fetch PR data, read logs, and push fixes

Quick Start

Start monitoring the current branch by invoking /pr-watch to watch CI status and apply fixes as needed.

Frequently Asked Questions about pr-watch

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

FAQPage Schema
How do I automatically fix CI failures on a pull request?

You can automatically fix CI failures by monitoring the pull request's status, reading failure logs, and applying targeted minimal code changes as new commits. This skill automates that entire process locally using the gh CLI to fetch logs and push fixes.

Can I monitor CI status locally and auto-merge pull requests when checks pass?

Yes, you can monitor CI status locally and optionally auto-merge pull requests when all checks pass. The skill continuously watches the PR's CI status and can trigger a merge automatically once the pipeline turns green.

Do I need the gh CLI installed to watch PRs and apply fixes?

Yes, you need the gh CLI installed and authenticated to use this PR monitoring and auto-fix workflow. It relies on the gh CLI integration to query CI status, fetch pull request data, and read failure logs locally.

What is the best way to debug failing CI checks without manually reading logs?

The best way to debug failing CI checks without manual log reading is to use an automated watcher that reads failure logs and applies minimal fixes. This skill parses CI logs locally, identifies the failure, and pushes corrective code commits automatically.

How does an automated pull request watcher apply code fixes?

An automated PR watcher applies code fixes by querying CI status, reading the specific failure logs, and generating minimal code changes. It then pushes these targeted fixes as new commits to your pull request branch.

Limitations of automatically fixing CI failures from local development environments?

A limitation of automatically fixing CI failures locally is that it applies minimal code changes based on log readings, meaning complex architectural failures may require manual intervention. It also depends entirely on local gh CLI access and proper authentication to push commits.