Standup Sync

THE PROBLEM. Every standup, status email and client update starts the same way: a developer scrolls through git log trying to reconstruct what they got done. Commit messages rarely help ("fix stuff", "wip"), so people open diffs, jump between branches and piece the week together from memory, then write it up again for the team, Slack and the client. It is slow, repetitive and error-prone: unmerged branch work gets forgotten, and reverts or formatting changes get reported as progress. THE SOLUTION. Standup Sync is a web app that writes those updates from the code itself. It reads the actual changes in a git repository over a date range, keeps only the meaningful ones, and produces ready-to-post Slack, Email and Standup updates, each in a developer version and a client version. WHO IT'S FOR. Developers preparing standups, team leads summarizing a week, and freelancers or agencies reporting to non-technical clients. HOW THEY USE IT. Paste a repository URL (any git host; private repos with a Personal Access Token), pick a range such as "last 7 days", and press Sync My Standup. A live tracker shows each step, then the six updates arrive: switch formats, toggle Developers and Clients, and copy with one click. Per-developer highlights show who shipped what. WHY IT'S CREATIVE AND UNIQUE. Changelog tools repeat commit messages, count every commit, usually read one branch and write one technical format. Standup Sync does the opposite: - IT READS THE DIFFS, NOT THE MESSAGES, so "fix stuff" still becomes "Fixed duplicate charge on payment retry". - IT REPORTS ACCOMPLISHMENTS ONLY. Merges, lock files, spacing-only edits and reverts (with the commit they undo) are removed in code; the AI tags each remaining change MAJOR or MINOR, and only major ones are reported. - IT COVERS EVERY BRANCH, including unmerged feature work. - IT WRITES FOR THE AUDIENCE: file and function names for developers, plain-English outcomes for clients, in the same run. HOW IT SOLVES THE PROBLEM EFFECTIVELY AND EFFICIENTLY. - ACCURATE: reports come from the code itself, across every branch, with noise filtered out. 102 automated tests, including runs against real public repositories, cover the pipeline. - CONCISE BY DESIGN: strict limits (Slack 3–6 bullets, email under 300 words, standup at most three lines per person) are enforced in code as well as in the prompt, so updates stay short enough to post as-is. - EFFICIENT: only two of five steps use an LLM, which only sees commits that survive the filter, so a typical run costs a few cents. Clones fetch only what a report needs: on microsoft/vscode, collecting a week of commits dropped from 807 to 143 seconds. - ONE RUN, SIX OUTPUTS: the same week never has to be rewritten for each audience.