pr-watcher

Monitor GitHub pull requests, check CI status, and post shipit messages.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/akshatdalton/skills --skill pr-watcher-akshatdalton
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-watcher
Source: https://github.com/akshatdalton/skills/tree/main/pr-watcher
Command: npx skills add https://github.com/akshatdalton/skills --skill pr-watcher-akshatdalton

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires github-api, json, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill simplifies the process of monitoring and managing GitHub pull requests, automating tasks like CI completion checking, auto-fixing safe failures, and posting shipit when clean.

Core Features & Use Cases

  • PR Monitoring: Keeps track of PRs and their CI states.
  • Auto-Fix Safe Failures: Automatically resolves safe failures within PRs.
  • Shipit Posting: Posts shipit on clean PRs, merging WIPDP PRs against main.
  • Use Case: A developer can use this Skill to set up a watcher tab in Claude Code, allowing them to monitor their PRs without manually checking them.

Quick Start

Set up the /pr-watcher Skill and use commands like 'add <PR url>' to add a PR to watch.

Frequently Asked Questions about pr-watcher

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

FAQPage Schema
How do I automate monitoring GitHub PR CI status?

Automate GitHub PR CI status monitoring by setting up a watcher tab in Claude Code to track pull requests, check completion states, and post shipit messages automatically when builds are clean.

Can I automatically fix safe failures in GitHub pull requests?

Yes, auto-fixing safe failures within GitHub pull requests is supported natively. The monitoring process detects safe CI failures and automatically resolves them without requiring manual code intervention.

How do I post shipit messages on clean PRs automatically?

Post shipit messages automatically on clean PRs by integrating watcher tracking with the GitHub API. The automation verifies CI completion and posts shipit, merging WIPDP PRs against main.

Do I need GitHub API access to monitor pull requests?

Yes, GitHub API access is required to monitor pull requests. The automation depends on API integration and a shared state file for watch tracking to check CI status and post updates.

What is the best way to track multiple GitHub PRs without manual checking?

The best way to track multiple GitHub PRs without manual checking is using an automated watcher tab in Claude Code. Add pull requests via their URL to continuously monitor their CI states and auto-fix safe failures.

Why does PR monitoring require a shared state file?

PR monitoring requires a shared state file for watch tracking to persist the list of monitored pull requests and their current CI statuses across sessions. This ensures continuous automated checks and accurate shipit posting.