LazyLead: a morning brief for engineering managers, written overnight by a local Gemma, with no GitHub tab needed

Description and use

LazyLead automatically generates a daily brief of GitHub PR activity and notifies managers only about overdue reviews, PRs without reviewers, or unanswered questions, reducing manual effort.

Problem

Engineering managers lack time to review GitHub PRs each morning, leading to missed overdue reviews and unanswered questions.

Outcome

LazyLead reduced API calls from 1,013 to 537 and processing time from 450 s to 60 s, limiting "no reviewer" lists from 400 lines to 10 lines with summary, and keeping other services on the same server with negligible impact.

Workflow

• 1. Run on a server at 3 AM
• 2. Read team GitHub activity via API
• 3. Code extracts facts (counts, mentions, PR status)
• 4. Gemma 4 (Ollama) summarizes threads, identifies questions, writes nudges and TL;DR
• 5. Validate Gemma output against facts
• 6. Generate brief page
• 7. Optionally push alerts via ntfy

Evidence

LazyLead reads the team's GitHub every night on your own machine, writes one page, and (optionally) pushes to the manager's phone only when a review is overdue, a PR has no reviewer, or a question is still unanswered.

Source

The first run was humbling: 1,013 GitHub API calls and 7.5 minutes for one day of data, a silent stop at 500 PRs, and a brief listing 400 PRs "with no reviewer".

Source

After the fixes: Collecting one day 450 s, 1,013 API calls → 60 s, 537 API calls.

Source

Gemma 4:e4b-it-qat (6.1 GB, quantization‑aware trained) on Ollama, on a 4‑core ARM server with no GPU.

Source