Add git lrc stats command for review history CLI

[fuleinist]

Problem

Every git commit with git-lrc embeds review metadata in the commit message: LiveReview Pre-Commit Check: ran (iter:N, coverage:X%). However there is no way to query or visualize this history from the CLI — developers must manually parse git log to understand their review coverage over time.

Solution

Add a git lrc stats (and alias lrc stats) command that:

• Parses LiveReview Pre-Commit Check: lines from git log for the current repo
• Shows a per-repo summary: total reviewed/vouched/skipped commits, average coverage, average iterations per commit
• git lrc stats --last 30 — last N days breakdown (default: all time)
• git lrc stats --json — outputs machine-readable JSON for CI dashboards or scripting

Example output:

$ git lrc stats
Review History (all time)
✅ Reviewed : 47 commits  (avg iter: 2.3, avg coverage: 74%)
👍 Vouched  : 12 commits
⏭️ Skipped  :  5 commits
Total      : 64 commits

Example JSON output (--json):

{
  "total": 64,
  "reviewed": { "count": 47, "avg_iter": 2.3, "avg_coverage": 74 },
  "vouched": { "count": 12 },
  "skipped": { "count": 5 }
}

Use case

Developers and teams want to understand review coverage trends over time without opening the browser UI. This is especially useful for team leads tracking how well AI-generated code is being reviewed across a sprint or time period.

Scope

• Single new subcommand in cmd/stats.go (or similar)
• Reuses existing git-log parsing logic already present in the codebase
• No new API calls, no network access, no external dependencies
• Target: small, focused — no UI changes needed

[iconicvenom]

First contribution here!😁
Planning to add a lrc stats command that parses the LiveReview Pre-Commit Check: trailers out of git log and prints a per-repo summary --last and --json flags included, with unit tests for the parsing logic. Is the output format in the issue still accurate, or has it shifted since then?

[shrsv]

tldr: can we think of this from a filtering, grouping, aggregating and general git history query feature?

Hi @fuleinist and @iconicvenom - this is a good initiative overall I feel. Just to provoke some thought around this - what are some usecases you think will be useful from a day to day team functioning perspective?

1. Something goes wrong in prod - we want to find whether the associated particular commit was reviewed or not; if so what are the records
2. We want to track the review efforts within a team, and improve it over time to get higher coverage (just an aggregate)
3. Find overall stats on a particular PR (branch <-> main) and post it somewhere for review (maybe even in the PR thread)
4. ...

I recommend thinking on these aspects a bit -- because as to the implementation part -- maybe it'd be a good idea to have "filters" first on the whole of commit log, and then build stats as a module on top of it.

One approach I can think of is a duckdb based approach. That is - build a table of the commit log using duckdb:

https://duckdb.org/docs/current/guides/snippets/analyze_git_repository

Then allow any query on top of it. And maybe have some query aliases for quick access (defaults + configurable).

This will give a generic reporting engine upon which a whole host of usecases can be supported from a team lead + engineer perspective.

Hopefully that sheds some light on how I think of this whole problem.

As to next action - I recommend refining your proposal on the problem + solution in a bit more details - so we can settle on an execution scope.