pr-merge-watcher

Monitor merged pull requests and update associated Notion tickets to 'Done' status.

Updated Aug 23, 2026

Search Tags:#automation #project management #ci/cd #pull request #github #notion

Ready to run

npx skills add https://github.com/christian-byrne/ticket-to-pr-pipeline --skill pr-merge-watcher

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pr-merge-watcher
Source: https://github.com/christian-byrne/ticket-to-pr-pipeline/tree/main/skills/pr-merge-watcher
Command: npx skills add https://github.com/christian-byrne/ticket-to-pr-pipeline --skill pr-merge-watcher

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @pipeline/client, gh, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that your project management tool (Notion) accurately reflects the status of your code deployments by automatically updating ticket statuses when a Pull Request is merged.

Core Features & Use Cases

Automated Status Updates: Scans for merged Pull Requests associated with open tickets.
Notion Synchronization: Updates the corresponding Notion ticket to 'Done' upon successful PR merge.
Handles Stale Tickets: Addresses scenarios where the agent might have been closed before a PR was merged.
Use Case: After a feature is deployed, this skill automatically marks the related task in Notion as complete, keeping your project board up-to-date without manual intervention.

Quick Start

Run the pr-merge-watcher skill in batch mode to automatically update all merged PRs.

Frequently Asked Questions about pr-merge-watcher

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

FAQPage Schema

How do I automatically update Notion ticket status when a GitHub pull request is merged?▼

To automatically update Notion ticket status upon a GitHub pull request merge, this Skill monitors merged PRs and transitions associated tickets to 'Done'. It integrates with a pipeline API to queue Notion updates, keeping project boards synchronized without manual intervention.

How does synchronizing merged pull requests with Notion work?▼

Synchronizing merged pull requests with Notion works by scanning for merged PRs associated with open tickets, then using a pipeline API to transition the ticket states and queue Notion updates. This ensures your project management tool accurately reflects code deployment status.

Does the pr-merge-watcher Skill handle stale tickets if the agent was closed before a PR merge?▼

Yes, the pr-merge-watcher Skill handles stale tickets by addressing scenarios where the agent might have been closed before a PR was merged. Running it in batch mode automatically updates all merged PRs and marks the related Notion tasks as complete.

Do I need a pipeline API client and GitHub CLI to automate closing Notion tickets from PR merges?▼

Yes, you need the pipeline API client and GitHub CLI dependencies to automate closing Notion tickets from PR merges. These tools allow the Skill to monitor repository events, access pull request data, and queue status updates for your project board.

What's the best way to keep a Notion project board up-to-date with CI/CD deployments?▼

The best way to keep a Notion project board up-to-date with CI/CD deployments is automating status updates via PR merge monitoring. This Skill scans for merged code changes and automatically transitions corresponding tickets to 'Done', eliminating manual project management overhead.