GitHub Monitor

Monitor watched GitHub repositories for stale PRs, issues, and releases.

Updated Jun 3, 2026
One-click install
npx skills add https://github.com/swarm-ai-research/aeon --skill github-monitor-swarm-ai-research
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: GitHub Monitor
Source: https://github.com/swarm-ai-research/aeon/tree/main/skills/github-monitor
Command: npx skills add https://github.com/swarm-ai-research/aeon --skill github-monitor-swarm-ai-research

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the ongoing task of watching multiple GitHub repositories for actionable signals, reducing manual triage and ensuring timely responses.

Core Features & Use Cases

  • Read the list of watched repos from memory/watched-repos.md and monitor those repositories.
  • Query GitHub for open PRs, new issues, and new releases using gh or API.
  • Apply the tiering model (ACT NOW / REVIEW / INFO) with per-tier caps and dedup logic.
  • Produce a single consolidated notification with explicit next actions and log outcomes for traceability.
  • Use memory/logs to maintain context across runs for continuity and auditing.

Quick Start

Configure your watched repos and run the monitor to begin receiving a single, actionable notification.

Frequently Asked Questions about GitHub Monitor

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

FAQPage Schema
How do I monitor multiple GitHub repos for stale pull requests and new releases?

To monitor multiple GitHub repos for stale pull requests and new releases, you configure a watched repositories list in memory. The tool queries GitHub via gh calls and applies a tiered urgency model to produce a single consolidated notification with explicit next actions.

What is the best way to automate GitHub issue and PR triage across multiple repositories?

Automating GitHub issue and PR triage across multiple repositories is best handled by applying a tiered urgency model with per-tier caps and dedup logic. This approach processes actionable signals from watched repos into a single consolidated notification.

Can I consolidate GitHub notifications for new issues and releases into a single alert?

Yes, you can consolidate GitHub notifications for new issues and releases into a single alert. The monitor gathers PRs, issues, and releases, applies tiered urgency caps, and produces one structured notification with clear next actions.

How do I set up tiered urgency levels for monitoring GitHub repositories?

To set up tiered urgency levels for monitoring GitHub repositories, you configure the monitor to apply an ACT NOW, REVIEW, and INFO tiering model. It caps results per tier and deduplicates signals to ensure deterministic behavior.

Does GitHub repo monitoring work with the gh CLI for automated alerts?

GitHub repo monitoring works directly with the gh CLI for automated alerts. It uses gh calls to gather open PRs, new issues, and new releases, ensuring deterministic behavior by reading memory and config files.

How do I maintain context across automated GitHub monitoring runs?

To maintain context across automated GitHub monitoring runs, the tool uses memory logs to track outcomes for continuity and auditing. This ensures that previous signals are deduplicated and context is preserved for future executions.