Stats
This page is generated from docs/guide.en.md · Edit this page on GitLab
An MR funnel, a distribution of the scores, the weekly evolution of the average score (“is quality improving?”), weekly activity, a table per project (with the resolution rate, a trend ▲/▼ and the last commit — date, author, link to the commit on its forge), a Top 5 of the repositories with the most recent activity (last commit with date AND time — several repositories push on the same day, and without the time the ranking looks arbitrary —, author, link; repositories whose MR fetching is unticked are excluded from it, as are inactive repositories: we no longer follow them), a token cost (a pie chart per call type + the average cost per reviewed MR), a summary of the sessions. Commit activity is fetched live from each repository's forge, across all branches (loaded separately, best-effort: nothing breaks if a forge is unreachable).
The most expensive reviews, next to the sessions: a review carried “the average” for want of an owner on its calls, and there was no way to say which one had eaten the budget. Each row opens its report, and the report itself says what it cost.
What goes in versus what comes back: characters sent per character received, per call family. A ratio that climbs points at an over-long template or a linked repository tripling every prompt — not an unavoidable cost. Both columns had been written since forever and read by nobody.
Verifications: green rate per repository, least green first — “which repository breaks the most?” had no answer.
The most expensive sessions. Five sessions, most to least expensive in estimated tokens. A prompt that makes the AI re-read three repositories for nothing shows up straight away. Token usage is now attached to the session that spent it, which is also what makes this ranking possible.
Findings that keep coming back. The same finding raised on at least three merge requests of the same repository: that is the raw material of a review rule, and Make it a rule opens the form pre-filled — the path_match derived from the files involved, the finding as the content.
The same findings, across repositories. The card above only compares a finding with merge requests of the same repository, so a finding raised twice on one and once on another never reached its three anywhere. This twin catches exactly that case — three merge requests, at least two repositories — and proposes a rule scoped to no repository and no path (a ** trigger: two unrelated repositories share no path prefix worth deducing).
Every number is a door. Clicking “worst 5.5” or “pending 3” opens Reviews filtered on that repository, at the right stage — instead of leaving you to find by hand what the figure points at.
Project activity — last 6 months. Answers “which repositories are alive, which are asleep”. One horizontal bar per tracked repository (active AND MR fetching ticked), ordered from the longest to the shortest, with the name in full on the left and the total on the right. The chart has a fixed height and scrolls: twenty repositories read fine without pushing the rest of the page away, and without any name being truncated — in columns, each got only 65 px and all of them ended up cut.
The length is the number of active days — the days on which at least one commit landed — and not the number of commits. A working day means the same thing everywhere, whereas a commit count mostly measures style: squashing or not changes the count fortyfold for the same work, and one inflated repository would crush all the others. The measure is also bounded (about twenty working days a month), so it is genuinely comparable from one repository to the next. The commits stay available on hover.
- The bar is stacked by month, one colour per month, oldest on the left to most recent on the right — time reads in the reading direction, and the legend under the chart gives the mapping. The hues follow a cold → warm sequence rather than a rainbow: months follow one another, and the order must stay readable even without looking at the legend. The length gives the volume, the distribution says whether the activity is recent or old — two hundred commits concentrated five months ago do not describe the same project as two hundred steady commits.
- The current month is not over: it is marked with an asterisk in the legend, so you do not read a drop where there is only a month in progress.
- A repository with no commit at all over the last two months gets its bar desaturated and its name in grey italics — desaturated rather than flattened to plain grey, so you can still read when it stopped, which is often the question you are asking in front of it. It stays in the list — that is exactly what you came to see — but it does not get confused with a merely quiet project. One empty month happens to everyone; two draw a slope.
- Hovering a bar gives the detail: active days and commits month by month, distinct contributors of the busiest month, and the reason when the repository is unreachable.
- Clicking a bar — the whole row, label included — opens the project over 12 months: six months say who is moving, twelve say in which direction. A repository quiet for two months after ten sustained ones does not tell the same story as a repository dead for a year, and the overview cannot tell them apart. The window gives the total of days, commits and contributors, the busiest month and the last activity — two markers you would otherwise hunt for by eye on the chart.
What is left out of the count: bot commits (Dependabot, Renovate, GitHub Actions, Mergify). Without that filter, an abandoned repository updated every week by a bot would keep a few active days a month and would never be flagged asleep — the exact false positive this chart is meant to avoid. A human committing from a forge's web interface, on the other hand, counts normally.
Repositories are queried four at a time: in series, twenty repositories add up their network round trips and the first load takes tens of seconds; all at once, the forge answers with a refusal. Two views asking for the same repository at the same moment (the overview and the detail window) share the same work instead of paying for it twice.
The counts are cached by month: a closed month no longer changes, only the current month is refreshed (at most once every half hour). Without that, six months of history would be re-paginated from the forge every time the tab is opened. On GitLab the count covers all branches; on GitHub the default branch only — listing them all there would cost dozens of calls per repository, and the screen says so rather than letting you believe in a complete count. An unreachable repository keeps its bar, with the reason on hover.
Every chart displays the question it answers. The token total is a lower bound (the agent's internal work is not counted).