The problem
A daily update often starts with reconstructing yesterday: opening repositories, checking pull requests and remembering what changed. A useful standup tool should help recover that context while leaving the developer in control of the final message.
Design and engineering choices
Start with selected sources
Repository collection is an explicit choice. Standup Auto gathers default-branch commits, authored pull requests and submitted reviews from the selected GitHub sources. Source links let a developer check the activity behind a draft instead of accepting a detached summary.
Keep the draft editable
The Today screen separates yesterday’s activity from manual plans and confirmed blockers. A developer can reorder or remove items, undo a change, save a version and mark the result reviewed. Synchronization preserves existing edits rather than replacing the author’s wording.
Make sharing a deliberate step
The application provides copy formats for a reviewed daily update. Nothing is automatically posted to a team channel. The weekly view brings reviewed daily updates together, deduplicates highlights and offers an editable recap with copy and download options.
Separate interface and server responsibilities
React and TypeScript provide the interface, with TanStack Query handling server state. Express handles the backend. The repository documents GitHub OAuth with PKCE, encrypted tokens and server sessions, plus SQLite for local development and PostgreSQL for the hosted environment.
How to use Standup Auto
- Select the repositories whose activity should be collected.
- Review the activity and follow source links when more context is needed.
- Edit yesterday’s summary, add your plan and confirm any blockers.
- Save and review the draft, then copy the update when you are ready to share it.
Scope and practical limits
- Drafts use rules grounded in GitHub metadata. The project is not presented as an LLM-generated standup service.
- Future plans stay manual. A commit history cannot reliably infer what someone intends to do next.
- Scheduled synchronization needs a host scheduler. Private repository access requires additional GitHub authorization.