← All features
Plain summaries

Every pull request, explained in one sentence.

When a PR merges, its diff is read once and turned into a sentence a non-technical reader understands. The code is never stored, and you can exclude any repository.

Pending PRs · plain summaries onwritten at merge · code not stored
14dMigrate payment webhooks to queueacme/api-gateway #1284 · truizRoutes Stripe notifications through a queue so none are lost when the service is saturated.
11dRate limiter per installationacme/api-gateway #1301 · apetitCaps how many API calls each customer can make.
4dFeature flags for GHES connectionsacme/web #872 · truizLets us enable Enterprise connections customer by customer.
2dTabular numerals in tablesacme/web #880 · lea-mAligns digits so numbers are easier to compare.
1Read once, in memoryThe diff is loaded at merge, summarized, then discarded. Nothing is written to disk.
2Our own modelsSummaries are produced by models Squadlog runs on its own servers. No third-party AI, no training.
3Where they appearMember profile, pending PRs, timeline, reports and the Monday digest. Toggle them per user.
Excluded reposRepositories you list in Settings are never read, even at merge.
LanguageSummaries can be written in a language independent from the interface.
Opt-outA member can opt out; their commits then show metadata only.

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.

Who it is for

For everyone who used to ask “so what did you ship?”

Founder or CEORead engineering like any other teamA list of sentences, not a list of branch names. Enough to follow, not enough to micromanage.
Product managerKnow when it actually mergedSee the feature you specified land, in words you can paste into release notes.
Engineering managerPrepare 1:1s with factsThe member profile tells the month in plain words before the conversation starts.
Questions

About plain summaries

All answers →
  • No. The diff is read once in memory to write the sentence, then discarded. Only the sentence, the PR number and metadata are kept.
Other features