Can AI summarize GitHub activity?

Yes. With Jarvis (getjarvis.eu), connect GitHub via OAuth and ask: "summarize GitHub activity in our repo this week", "what did Maria ship since Monday?", or "summarize open PRs in the auth repo". Press Cmd+/ on Mac or Ctrl+/ on Windows. Jarvis pulls commits, PRs, issues, and reviews through the GitHub API, then routes the summarization to a frontier model for nuanced output. Output covers what shipped, what's in review, what's blocked, and who's been active. Persistent memory remembers your repos and team naming patterns across sessions. OAuth tokens use AES-256-GCM and EU data residency for GDPR compliance. Free tier handles daily summaries; Pro at $16/month and Unlimited at $32/month scale to bigger repos. Works on Mac, Windows, and Linux. Same flow works for GitLab and Bitbucket when those connectors are enabled.

Useful GitHub summaries answer four questions: what shipped, what's in flight, what's blocked, and who did what. Jarvis pulls each through GitHub's REST and GraphQL APIs in parallel. For "what shipped": merged PRs in the time range with PR titles, descriptions, and linked issues. For "what's in flight": open PRs with review status (approved / changes-requested / waiting-review) and stale-review flags. For "what's blocked": open PRs older than 5 days without recent activity, plus issues with the blocked label. For "who did what": per-author breakdown of merged PRs, opened issues, and reviews. Routing is a frontier model for the synthesis. The output appears in the Jarvis floating bar grouped by category, with PR/issue links so you can drill into any item. For very large repos (1000+ activity items in the range), Jarvis routes to a frontier model.

Install Jarvis (Mac, Windows, Linux). Sign in. In Settings → Integrations connect GitHub via OAuth — request read scope on your repos. Press Cmd+/ on Mac or Ctrl+/ on Windows. Type a summary request: "summarize GitHub activity in our main repo this week", "what did the engineering team ship since Monday?", "summarize open PRs in repos I'm involved with", "what's blocked in the platform team's repos?". Jarvis returns a structured digest in 15-45 seconds. To narrow: specify a repo ("only in jarvis-site-v1"), a person ("only Mihai's activity"), or a label ("only PRs tagged customer-facing"). To turn the summary into something durable: "draft this as a Slack message in #engineering" or "add this as a new Notion page in our weekly digest database" — both work if those connectors are enabled.

Code & tickets