feature
When the run prompt supplies a Workflow correlation ID, include the exact marker <!-- aeon-dispatch:<ID> --> in every PR body you create. This is a machine-checked chain receipt: do not alter, omit, or place it only in the final response.
${var} — Selector
target[:arg] [--fix-issues],target ∈ {watched, external, dormant}. Empty orwatched= build a feature on every watched repo (one PR each);external:<owner/repo>= one best enhancement on that external repo;dormant= revive the highest-scoring dormant repo. A leadingbuild:<owner/repo | issue-url | free-text instruction>— the shape the Telegram "ship which opportunity?" force-reply sends viarepo-scanner's offer — is intercepted first and routed into the external branch on that target/instruction.--fix-issuesbiases the chosen branch toward fixing an open GitHub issue. Full grammar below.
This skill merges three repo-work modes behind one selector so no capability is lost:
| Branch | Selector | Per run | Repo source | Use it for |
|---|---|---|---|---|
| watched (§A) | empty / watched |
Iterates every watched repo, ships one PR per repo | memory/watched-repos.md |
Weekly broad sweep — keep every repo moving |
| external (§B) | external[:owner/repo[#N]] |
Single repo per run | memory/topics/repos.md catalog (or ${var} override) |
Targeted enhancement / issue fix on one repo |
| dormant (§C) | dormant[:owner/repo] |
Single dormant repo per run | memory/watched-repos.md scored by dormancy |
Reactivate a stale high-★ repo with one visible fix |
Today is ${today}. Read memory/MEMORY.md and the last 7 days of memory/logs/ before starting — and before notifying, drop anything already reported in the last ~3 days of logs.
Selector
Telegram force-reply interception — check this FIRST, before parsing anything else. If ${var} starts with build:, it is the "ship which opportunity?" force-reply that repo-scanner offers (routed here as feature with var="build:<the operator's reply>"). Strip the prefix with ${var#build:} and treat the remainder as an external build target/instruction — route it straight into the external branch (§B), reusing that branch's existing logic (do not run the watched or dormant branches for a build: value, and do not duplicate §B). Normalize the remainder into a §B target: