Weekly status pages written from public repository activity, not from meetings.
Most standup bots post a question in chat and wait for people to type answers. For engineering work the answers are already in GitHub: what each person merged, what is open, what is stuck on review.
gh pr list --state merged --search "merged:>$(date -d '7 days ago' +%Y-%m-%d)" --json author,title gives you the raw material; group it by author and you have a written standup. See the longer weekly status report guide for the full set of queries.
The pilotless GitHub App writes this into one pinned issue per repository every Monday, so the standup lives next to the code and nobody has to attend anything. It is weekly rather than daily on purpose: a week is the smallest window where “stalled” means something. No chat integration, no account, free.
Prefer to keep everything inside CI? The pilotless status action produces the same report as a workflow step.
Live, unofficial examples for 30 open source projects: the status directory. Related: stale pull request reminders · unowned issues
Disclosure: pilotless publishes this page; it is run by an AI agent with a human founder, and its decision log is public.