pr-merge-watcher

Monitor GitHub pull requests and update task states after merges.

Updated Apr 24, 2026
One-click install
npx skills add https://github.com/papeete-consulting-lab/banking-reliever --skill pr-merge-watcher-papeete-consulting-lab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-merge-watcher
Source: https://github.com/papeete-consulting-lab/banking-reliever/tree/main/.claude/skills/pr-merge-watcher
Command: npx skills add https://github.com/papeete-consulting-lab/banking-reliever --skill pr-merge-watcher-papeete-consulting-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual effort of monitoring pull requests, updating task states after merges, and coordinating CI failure recovery workflows.

Core Features & Use Cases

  • PR Status Monitoring: Checks open GitHub pull requests linked to in-review tasks and transitions merged work into completed states.
  • CI Failure Handling: Detects failed pipelines, collects focused failure details, and dispatches remediation workflows while preventing duplicate fixes.
  • Task Board Synchronization: Refreshes task tracking views and identifies newly available work after dependency changes.

Quick Start

Use the pr-merge-watcher skill to check all open pull requests, update merged tasks, and handle any failing CI pipelines.

Frequently Asked Questions about pr-merge-watcher

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

FAQPage Schema
How do I automate pull request monitoring and update task states after merges on GitHub?

Pull request monitoring is automated by checking open GitHub pull requests linked to in-review tasks and transitioning merged work into completed states. The Skill updates task metadata and refreshes task tracking views automatically after detecting repository changes.

What is the best way to handle CI failures and dispatch remediation workflows for pull requests?

CI failure handling detects failed pipelines, collects focused failure details, and dispatches automated remediation workflows. It prevents duplicate fixes by applying idempotent failure recovery handling to avoid triggering redundant tasks for the same failing pull request.

Can I use the GitHub CLI to synchronize a task board with repository pull request changes?

Yes, GitHub CLI operations are required to synchronize task boards with repository changes. The Skill refreshes task tracking views and identifies newly available work after dependency changes, keeping implementation tasks aligned with the pull request lifecycle.

How does task board synchronization work after a pull request dependency changes?

Task board synchronization works by refreshing task tracking views and identifying newly available work after dependency changes. It updates task metadata to keep implementation tasks synchronized with repository changes detected through GitHub pull request monitoring.

Does pr-merge-watcher support idempotent failure recovery for duplicate CI fix workflows?

Yes, pr-merge-watcher applies idempotent failure recovery handling to prevent duplicate fixes when dispatching remediation workflows. It ensures that repeated CI failures on the same pull request do not trigger overlapping automated recovery tasks.

When should I not use automated merge tracking for GitHub pull request lifecycle management?

Automated merge tracking is not ideal for workflows outside GitHub-based development environments, as it requires GitHub CLI operations. It is specifically designed for review queues, merge detection, and CI failure coordination within GitHub repository workflows.