watch-pr

Automate GitHub pull request review resolution, CI fixes, and merging.

1|Updated Dec 8, 2025
One-click install
npx skills add https://github.com/adamayoung/popcorn --skill watch-pr-adamayoung
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: watch-pr
Source: https://github.com/adamayoung/popcorn/tree/main/.claude/skills/watch-pr
Command: npx skills add https://github.com/adamayoung/popcorn --skill watch-pr-adamayoung

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh.

What problem does it solve?

This skill removes the friction of managing pull requests by automating the repetitive cycle of addressing review comments, fixing failing CI checks, and merging code once everything is green.

Core Features & Use Cases

  • Automated Review Handling: Automatically resolves review threads, replies to feedback, and tracks progress via a run ledger to prevent redundant work.
  • CI Failure Resolution: Integrates with diagnostic tools to fix linting, build, or test failures, capping attempts to ensure the process remains efficient and safe.
  • Merge Orchestration: Safely manages branch updates and squashed merges, ensuring the repository remains clean and the PR is only merged when all quality gates are satisfied.

Quick Start

Invoke the watch-pr skill to monitor the current branch and automatically handle all review threads and CI checks until the PR is ready to merge.

Frequently Asked Questions about watch-pr

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

FAQPage Schema
How do I automate GitHub pull request review and CI fixes?

To automate GitHub pull request review and CI fixes, you can use an orchestration skill that iteratively resolves review threads, runs local linting and testing to fix failing status checks, and performs a final merge once all quality gates pass.

What's the best way to automatically merge a pull request after CI passes?

The best way to automatically merge a pull request after CI passes is to use an automation tool that monitors CI status checks, remediates failures through iterative code fixes, and executes a safe squashed merge once all checks are green.

Do I need the GitHub CLI installed to automate pull request lifecycle management?

Yes, you need the authenticated GitHub CLI installed to automate pull request lifecycle management, as the process relies on it to interact with GitHub APIs for resolving review threads, monitoring CI checks, and executing branch merges.

How does automated CI failure resolution work for pull requests?

Automated CI failure resolution works by integrating with local diagnostic tools to identify linting, build, or test failures, then iteratively applying code fixes with a capped number of attempts to ensure safe and efficient remediation.

Can I target a specific pull request number for automated review handling?

Yes, you can target a specific pull request number for automated review handling, or you can operate directly on your current branch to automatically resolve review threads, reply to feedback, and track progress via a run ledger.

What are the limitations of automating pull request merges with local development tools?

Limitations of automating pull request merges include dependency on a local development environment to execute linting, testing, and build verification, as well as a capped number of attempts for fixing CI failures to prevent excessive automated modifications.