AI agent that monitors GitHub repos

GitHub Monitor is an aeon skill: Watch your GitHub repos across four views - a combined urgency monitor (stale PRs, new issues, releases), a new-issue triage queue, a release upgrade digest, or your own opened-PR tracker. Like every aeon skill it is one SKILL.md prompt file that runs unattended on your own GitHub Actions, on a schedule or when you trigger it, and sends what it finds to Telegram, Discord, Slack or email.

This skill is four focused views of the same GitHub surface. The combined monitor is the default; issues, releases, and prs each drill into one dimension with the sibling view's own filtering, ranking, and output format. Only the monitor and issues views take a repo scope; releases takes a repo list; prs takes no scope (it reads its config from aeon.yml/env).

Every aeon skill takes one optional text input, var, set in aeon.yml or typed in when you run it by hand. It picks the target or the mode for that run.

View selector + optional scope.

• empty → combined monitor over every repo in memory/watched-repos.md.
• owner/repo (a bare repo, no view keyword) → combined monitor scoped to that one repo.
• issues [scope] → new-issue triage queue. scope accepts owner/repo, org:foo, user:bar, or a bare login; empty = all repos owned by the authenticated user.
• releases [repo,repo,…] → release upgrade-triage digest. Comma-separated repo list; empty = the built-in watch list.
• prs → status tracker for PRs this aeon instance opened across external repos.
• add-repo:<owner/repo> → append owner/repo to memory/watched-repos.md, confirm, and end (the shape the Telegram force-reply sends - see the config-capture note in Shared setup). No view runs.

No extra API keys or MCP servers. It runs on the model you connected to aeon (a Claude subscription token, an API key, or another login).

Easiest: open Aeon Connect, sign in with GitHub and turn on GitHub Monitor. No clone, no terminal. To add it to an existing aeon repo from a shell, run:

Then switch it on in aeon.yml (the default schedule is filled in):

skills:
  github-monitor: { enabled: true, schedule: "0 9 * * *", var: "" }

New to aeon? Read the docs for how skills, schedules and memory fit together, or browse all skills.