The problem with PR titles
Pull request titles are written for the people who will review the code: “refactor webhook consumer”, “fix #1284”, “bump partition job”. They are accurate and useless to anyone outside the team. Managers, product owners and founders end up asking developers to narrate their week, which costs everyone time.
Plain summaries replace that narration. When a PR merges, Squadlog writes one sentence about what changed for the product or the service, in words anyone in the company can read.
What is read, and when
The diff is read exactly once, at merge time, in memory, by a model that runs on Squadlog’s own servers. The sentence is kept; the diff is discarded. Nothing is sent to a third-party AI provider and nothing is used to train a model. Before and after that moment, Squadlog only handles metadata: authors, dates, numbers, sizes.
Repositories you exclude in Settings are never read, even at merge. Members can opt out individually; their PRs then show the title only.
Where summaries appear
In the pending PRs list, so a manager can decide which review to chase without opening GitHub. On each member’s profile, as the “In plain words” paragraph for the period. In the Monday digest and in weekly and monthly reports, where the week is told from the summaries of what merged.
Language and tone
Summaries are written in the language you choose per team, independently from the interface language. They describe what changed, never how well it was done; there is no adjective about quality and no comparison between people.