Monitor GitHub repositories for stale pull requests, new issues, and releases.
npx skills add https://github.com/anajuliabit/aeon --skill github-monitor-anajuliabit
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
GitHub activity can quietly pile up—stale PRs, untriaged issues, and important releases slip past without timely action.
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.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
Atrium-HermesSummarize daily pushes and merged PRs from watched repositories.
supersuit-techTrigger GitHub Actions CI and audit workflows, collect failure logs, and iterate until both pass.
gerald-icaAutomate GitHub PR reviews, issue triage, and CI/CD integration.
fxGenerate release-note summaries for GitHub Releases from changelog and PR bodies.
