GitHub Monitor

Monitor GitHub repositories for stale pull requests, new issues, and releases.

6|2|Updated May 21, 2026

Search Tags:#automation #monitoring #github #pull requests #issue triage #release tracking #ci alerts

Ready to run

npx skills add https://github.com/anajuliabit/aeon --skill github-monitor-anajuliabit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: GitHub Monitor
Source: https://github.com/anajuliabit/aeon/tree/main/skills/github-monitor
Command: npx skills add https://github.com/anajuliabit/aeon --skill github-monitor-anajuliabit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GitHub activity can quietly pile up—stale PRs, untriaged issues, and important releases slip past without timely action.

Core Features & Use Cases

Detect PRs needing attention: Finds open, non-draft PRs that are failing CI, have pending reviews, or have gone idle based on freshness windows.
Triage issues by priority: Surfaces new issues opened in the last 24 hours when they match high-priority labels like security, critical, p0, regression, outage, or incident.
Monitor releases by significance: Flags releases published in the last 24 hours and prioritizes major version bumps relative to what was previously logged.

Quick Start

Tell the agent to run the GitHub Monitor for a specific repository by setting var to "owner/repo", or leave it empty to monitor all watched repositories in memory/watched-repos.md.

Frequently Asked Questions about GitHub Monitor

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

FAQPage Schema

How do I monitor GitHub repositories for stale pull requests and untriaged issues?▼

To monitor GitHub repositories for stale pull requests and untriaged issues, run a scheduled automation Skill that executes authenticated gh API queries to classify open PRs and new issues into actionable priority tiers. It identifies idle PRs, failing CI checks, and high-priority issues using freshness and label rules.

What is issue triage automation and how does it work for GitHub?▼

Issue triage automation for GitHub works by querying newly opened issues and classifying them based on high-priority labels like security, critical, p0, regression, outage, or incident. It deduplicates issues using memory logs and consolidates findings into tiered ACT NOW or REVIEW notifications.

How do I track new GitHub releases and prioritize major version bumps?▼

Track new GitHub releases and prioritize major version bumps by running scheduled automation that flags releases published in the last 24 hours. It compares current releases against previously logged versions in memory to determine significance and escalates major version bumps for review.

Can I monitor all watched GitHub repositories or do I need to specify a single repo?▼

You can monitor all watched GitHub repositories by leaving the repository variable empty, which defaults to reading from memory/watched-repos.md. Alternatively, set the variable to a specific owner/repo string to monitor a single repository.

Do I need the gh CLI to authenticate GitHub API queries for release tracking and issue triage?▼

Yes, you need the gh CLI authenticated in your environment to execute GitHub API queries for release tracking and issue triage. The automation relies on gh API access to fetch PRs, issues, and releases, and to write structured run traces to memory logs.

What is the best way to get CI alerts for failing pull requests on a schedule?▼

The best way to get CI alerts for failing pull requests on a schedule is using recurring automation that queries open non-draft PRs, detects failing CI status, and classifies them into ACT NOW notifications. This ensures engineering teams receive consolidated, actionable alerts for immediate review.