PR Tracker

Track cross-repo pull request statuses via GitHub GraphQL and gh.

626|225|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/aaronjmars/aeon --skill pr-tracker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: PR Tracker
Source: https://github.com/aaronjmars/aeon/tree/main/skills/pr-tracker
Command: npx skills add https://github.com/aaronjmars/aeon --skill pr-tracker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents missed merges and stale pull requests by automatically auditing the status of PRs opened by an aeon instance across external repositories.

Core Features & Use Cases

  • Tracks merge and lifecycle states across repos: identifies recent merges (last 7 days), stale open PRs (> 7 days), active open PRs, and closed-but-not-merged PRs.
  • Maintains a rolling status memory: rewrites memory/topics/pr-status.md with a sorted table of the last 30 tracked entries.
  • Sends an actionable notification only when needed: skips notifications when there is nothing materially new, and logs results to memory/logs/${today}.md.

Quick Start

Audit the PRs opened by this aeon instance across configured external repos and notify me if any recent merges or stale open PRs need attention.

Frequently Asked Questions about PR Tracker

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

FAQPage Schema
How do I monitor cross-repo pull requests for stale detection?

Cross-repo pull request monitoring tracks recent merges, stale open PRs older than 7 days, and closed no-merge items using GitHub GraphQL via gh, updating memory with sorted status tables to prevent stale pull requests.

How do I automate release hygiene checks for dependency drift across multiple GitHub repositories?

Automating release hygiene checks involves auditing pull request lifecycle states across multiple repositories to detect missed merges and reduce dependency drift, logging daily results to memory and sending conditional notifications.

Can I filter GitHub pull request tracking by branch prefix and author?

Yes, pull request tracking can be filtered by a configurable author, an optional bot email, and a specific branch prefix to accurately audit PRs opened by an aeon instance across external repositories.

What is the best way to report unattended PR status without creating notification noise?

Unattended PR status reporting skips notifications when nothing is materially new, maintaining a rolling status memory of the last 30 tracked entries in a markdown table and logging daily results to reduce notification noise.

Does PR tracking work with gh search prs if GitHub GraphQL fails?

Yes, PR tracking uses GitHub GraphQL via gh as the primary method with a fallback to gh search prs, ensuring recurring background workflows and unattended PR monitoring continue functioning during API inconsistencies.