Name it and pick the repositories
Open Automations → New Automation. Name it and pick up to ten repositories to read.
Get a recurring report.
Some questions need asking every week: which dependencies fell behind, which issues need triage, what a competitor shipped. Save the question once as an automation and ProPR answers it on schedule, in a Markdown report that leads with what changed since last time.
Describe
Run isolated
Review in GitHub
Feature overview
Write the brief
Brief it the way you would brief a colleague: what to look at, what matters, how to lay out the report. Attach a policy or checklist as an input file.
Turn on Previous reports and the last reports feed the next run, so each one leads with what is new, changed or resolved.
Choose what it can reach
Every run reads its repositories and never commits or pushes. Add web access for outside research, or, on Claude Code and Codex, ProPR tools to read tasks, PRs and todos.
Put it on a schedule
Pick a preset or write a cron line. Schedules run in UTC, as often as every 15 minutes, and the form previews the next run.
Read the report
Each run lands in the automation's history with its Markdown report. On dry run, the report is the whole result.
A report today, work tomorrow.
On Claude Code or Codex, switch the autonomy to preview + approve and ProPR waits for your go-ahead before it turns the report into tasks, plans and todos. Other agents run automations as dry runs. The Automations guide covers the acting step and its limits.
What you get
A Markdown report on your schedule, built from a read-only look at your repositories, that leads with what changed since the last one.