Weekly code health brief for engineering leadership
Every Monday at 8am, your leads get a plain English read on code quality across every project, plus a spreadsheet that tracks the trend over time.
SonarCloud
Google Sheets
GmailEngineeringOperationsAI ReportsDaily DigestsEvery Monday at 8am, write a code health brief for our engineering leadership so nobody has to open a SonarCloud dashboard to know how we are doing.
Start with the SonarCloud "Projects — Search" operation to enumerate every project in our organization. Page through the results so the brief covers all of them, not just the first page.
For each project, use "Measures — Component" to read the current coverage, duplicated lines density, technical debt (the sqale_index metric), and the reliability, security and maintainability ratings. Then use "Quality Gates — Project Status" to get the current pass or fail state.
Use "Measures — Search History" to pull those same metrics from roughly one week ago for each project, and compare. This comparison is the whole point of the brief: lead with what actually moved rather than a wall of raw numbers.
In the narrative, call out the three projects that regressed the most and explicitly flag any project whose coverage fell by more than two percentage points. Also name anything that newly failed its quality gate, and give credit where a project genuinely improved.
If a project has no fresh analysis in the past week, or is missing one of the metrics, leave it out of the comparison rather than reporting a false regression, and note at the end of the brief which projects had no new data.
Append one row per project per week to a tracking spreadsheet using the Google Sheets "Append Values" operation so a trend line builds over time. Each row should carry the week's date, the project name, coverage, duplicated lines density, technical debt, the three ratings, and the quality gate state.
Then send the narrative brief to the engineering leads with the Gmail "Send a Message" operation. Keep the prose skimmable for a VP who does not read code: short paragraphs, plain language, no metric jargon, and a one line verdict at the top saying whether code health improved or declined overall this week. Let the spreadsheet carry the per project detail, and link to it from the email.
What does this prompt do?
- Reads every project in your SonarCloud organization each Monday morning and pulls the numbers that matter: test coverage, duplicated code, technical debt, and the reliability, security and maintainability ratings.
- Compares this week against last week and leads with what actually changed, naming the three projects that slipped the most.
- Flags any project whose test coverage dropped by more than two points, and any project that is now failing its quality gate.
- Logs one row per project per week to a spreadsheet so a trend builds over months, then emails the written brief to your engineering leads.
What do I need to use this?
- A SonarCloud account covering the projects you want in the brief
- A Google account for Gmail and Google Sheets
- A spreadsheet to hold the weekly tracking rows
- The email addresses of the engineering leads who should receive the brief
How can I customize it?
- Change the timing: Monday at 8am is the default, but any day and hour works.
- Change who gets it: send to a single VP, a leads alias, or a wider engineering list.
- Change the thresholds: the two point coverage drop and the top three regressions are both easy to adjust.
- Narrow the scope to a subset of projects if you only care about what is running in production.
FAQs
Do I need to understand the SonarCloud dashboard to read this?
What is technical debt in this report?
Will it still email us on a quiet week?
Does this work if we only have a handful of projects?
Can the brief go somewhere other than email?
Related templates
Stage a batch of filings overnight, then approve each completed form from a screenshot before anything is ever submitted.
Review every conversation Fin closed as resolved, judge which ones actually stuck, and see what the gap is worth against your bill.
Work every return, damage and warranty claim in one queue, with the order, the delivery date and a policy-backed recommendation already on screen.
See who is due, build a week of dinners on demand, swap anything you do not like, then send the recipe and grocery links yourself.
See every install this week day by day, with the crew, the homeowner, whether materials were ordered, and the latest jobsite photos.
See exactly which ingredients next week needs based on what you actually sold, adjust anything by hand, then build a one-click grocery cart.
Stop asking engineers how code quality is going.
Get one written brief every Monday that tells your leadership what moved, what slipped, and what needs attention.