github-monitor

${var} — 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.

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).

Shared setup (every view)

1. Read memory/MEMORY.md for high-level context.
2. Read the last 2 days of memory/logs/ — used for dedup in the monitor, issues, and releases views.
3. Parse ${var} into a VIEW and a SCOPE: