Why we built it
We kept running into the same problem across our own projects and client work. Someone (a CTO, a product manager, a client) would ask "what shipped this week?" and the answer was always scattered across pull requests, commit logs, and Slack messages.
Engineers shouldn't have to write status reports. And managers shouldn't have to read every PR to understand what's happening. GitLoom sits in between.
What it does
PR summaries. GitLoom reads every pull request and generates a plain-English summary of what changed and why. No jargon, no diffs, just a clear explanation that anyone on the team can understand.
Progress reports. At the end of each week (or any cadence you choose), GitLoom compiles a report of everything that shipped. Grouped by project, written for humans, ready to share with stakeholders.
GitHub-native. It connects directly to your GitHub repositories. No extra tools to install, no workflow changes for your engineers. They keep writing PRs the way they always have.
Where it is now
GitLoom is live at gitloom.ai and used by development teams to keep their stakeholders informed without adding process overhead.