stale-pr-check

Identify open pull requests older than 24 hours and infer blockers from pipeline labels.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/blucsigma05/tbm-apps-script --skill stale-pr-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stale-pr-check
Source: https://github.com/blucsigma05/tbm-apps-script/tree/main/.claude/scheduled-tasks/stale-pr-check
Command: npx skills add https://github.com/blucsigma05/tbm-apps-script --skill stale-pr-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents open pull requests from languishing unmerged by identifying PRs older than a threshold and reporting who or what is blocking them.

Core Features & Use Cases

  • Daily stale PR detection: Scans open PRs and filters to those older than 24 hours while skipping wip or draft PRs.
  • Blocking inference from labels: Maps pipeline and decision labels to likely blockers (author, CI/Codex, LT decision, or general triage).
  • Priority-based notifications: Sends a Pushover alert with a per-PR summary line, and escalates urgency for PRs over 72 hours.

Quick Start

Ask the system to run stale-pr-check to send a daily 8am report of open PRs older than 24 hours in tbm-apps-script, including the inferred blocking reason.

Frequently Asked Questions about stale-pr-check

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

FAQPage Schema
How do I identify stale pull requests and find out what is blocking them?

To identify stale pull requests, you can run a scheduled check that scans open PRs older than 24 hours, filters out drafts, and infers block reasons from pipeline labels. This prevents PRs from languishing unmerged.

How does stale PR detection handle work in progress or draft entries?

Stale PR detection handles draft entries by filtering out PRs labeled as wip or draft during the scan. This ensures daily stale alerts only target active pull requests that are actually ready for review and blocking continuous delivery work.

Can I receive daily notifications for old pull requests in my repository?

Yes, you can receive daily notifications for old pull requests by scheduling a check to run at 8am. It sends a Pushover alert with a prioritized summary line for each stale PR, escalating urgency with an urgent marker for PRs over 72 hours.

How do pull request labels infer who is blocking a merge?

Pull request labels infer blocking by mapping pipeline and decision labels to likely blockers like author, CI/Codex, or LT decision. This label triage mechanism helps identify the exact reason a PR is stalled so the right team can take action.

Does stale PR monitoring work for GitHub-style workflows?

Yes, stale PR monitoring works for GitHub-style workflows by listing PR metadata and computing age in hours. It applies to scheduled repository hygiene tasks that monitor continuous delivery work within standard GitHub pull request workflows.

What is the age threshold for escalating stale pull request alerts?

The age threshold for escalating stale pull request alerts is 72 hours. PRs exceeding this age receive an urgent marker in the notification routing, distinguishing them from standard stale alerts for PRs older than 24 hours.