PR Tracker

Monitor and report pull request statuses in GitHub repositories.

Updated Jun 17, 2026
One-click install
npx skills add https://github.com/aeoncity-demo/myaeon --skill pr-tracker-aeoncity-demo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: PR Tracker
Source: https://github.com/aeoncity-demo/myaeon/tree/main/skills/pr-tracker
Command: npx skills add https://github.com/aeoncity-demo/myaeon --skill pr-tracker-aeoncity-demo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes scripts (resource) components.

What problem does it solve?

This Skill automates the tracking of pull requests (PRs) opened in GitHub repositories, providing updates on merges, stale open PRs, and closures.

Core Features & Use Cases

  • Automated PR Status Updates: Tracks the status of PRs, including merges, stale open PRs, and closures.
  • Customizable Configuration: Identifies PRs opened by a specific author or with a specific branch prefix.
  • Reporting: Generates a report on PR statuses and updates it regularly.
  • Use Case: Ideal for developers or project managers who need to keep an eye on the status of multiple PRs across multiple repositories.

Quick Start

Run the PR Tracker Skill to check the status of all PRs opened by your team.

Frequently Asked Questions about PR Tracker

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

FAQPage Schema
How does pull request tracking identify which commits to monitor?

Pull request tracking identifies which commits to monitor through configurable filters. You can configure the tracker to identify target PRs specifically by their author or by using a defined branch prefix, ensuring the generated report focuses only on relevant activity.

How do I automate pull request monitoring for multiple GitHub repositories?

Automate pull request monitoring by configuring a tracker to check GitHub API endpoints for merges, stale open PRs, and closures. You can filter PRs by specific author or branch prefix to generate regular status reports across multiple repositories.

Do I need a GitHub token to track PR status automatically?

Yes, tracking PR status automatically requires GitHub API access and authentication via a GITHUB_TOKEN. This token authorizes the script to query repository data, identify stale open PRs, and generate activity reports without manual intervention.

What is the best way to track stale open pull requests in GitHub?

The best way to track stale open pull requests is using an automated monitoring script that queries the GitHub API. It identifies inactive PRs based on your configured criteria, such as specific branch prefixes or authors, and includes them in a generated status report.

Can I use gh to generate reports on pull request activity?

Yes, you can use the gh dependency to interface with the GitHub API and generate reports on pull request activity. The script tracks merges, closures, and stale PRs, updating the report regularly to reflect current repository statuses.

How does pull request tracking identify which commits to monitor?

Pull request tracking identifies which commits to monitor through configurable filters. You can configure the tracker to identify target PRs specifically by their author or by using a defined branch prefix, ensuring the generated report focuses only on relevant activity.