pr-poller

Poll GitHub pull requests and dispatch follow-ups for merged, closed, and Renovate-labeled PRs.

18|Updated Feb 14, 2020
One-click install
npx skills add https://github.com/subroh0508/colormaster --skill pr-poller
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-poller
Source: https://github.com/subroh0508/colormaster/tree/main/.claude/skills/pr-poller
Command: npx skills add https://github.com/subroh0508/colormaster --skill pr-poller

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

pr-poller removes the manual burden of continuously checking GitHub for merged, closed, and Renovate-related pull requests, then routing each result to the correct follow-up workflow without duplicate processing.

Core Features & Use Cases

  • Pull Request Polling: Collects merged and closed PRs from GitHub using the gh CLI and identifies items that still need retrospectives.
  • Dependency Upgrade Routing: Detects open PRs with Renovate-related labels and dispatches them to dependency-upgrade handling.
  • Operational Guardrails: Uses lock-based concurrency control, lookback tracking, deduplication, retry logic, and threshold checks to support reliable recurring execution.
  • Use Case: A team member starts the skill after a merge window, and it automatically finds unprocessed PRs, skips already handled items, and reports what follow-up actions were triggered.

Quick Start

Use the pr-poller skill to scan recent merged and closed pull requests, dispatch any needed retrospective or dependency-upgrade follow-ups, and summarize the results.

Frequently Asked Questions about pr-poller

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

FAQPage Schema
How do I automate GitHub pull request polling for retrospectives?

Automating GitHub pull request polling for retrospectives requires scanning merged and closed PRs via the gh CLI, applying deduplication and lookback tracking, then sequentially dispatching follow-up tasks to trigger needed retrospective workflows without manual checks.

What's the best way to track merged Renovate pull requests for dependency upgrades?

Tracking merged Renovate pull requests for dependency upgrades is handled by detecting open PRs with Renovate-related labels and routing them to dependency-upgrade handling with lock-based concurrency control and threshold-based decisions.

Does automated PR polling work with local Claude Code recurring workflows?

Automated PR polling works with local Claude Code recurring workflows by utilizing cached run-state files for lookback tracking, retry handling, and lock-based concurrency to support reliable sequential handoff to downstream tasks.

Do I need the gh CLI installed to poll GitHub pull requests?

You need the gh CLI installed to access GitHub pull request polling and follow-up dispatch, as it collects merged and closed PRs, identifies items needing retrospectives, and detects Renovate-labeled dependency upgrades.

How does recurring PR polling avoid duplicate processing of closed pull requests?

Recurring PR polling avoids duplicate processing of closed pull requests by maintaining cached run-state files for lookback tracking and deduplication, ensuring previously handled items are skipped during sequential downstream task dispatch.