[sagnik11]

What

A new autter badge subcommand that gives any repository a README badge reading AI-written | 72%.

$ autter badge
AI-written: 72%  (912 AI-accepted of 1266 added lines)
Window: 58 non-merge commits since 2026-08-05, 54 with authorship notes

README snippet (copied to clipboard):

  [![AI-written](https://img.shields.io/badge/AI--written-72%25-5b5bd6)](https://autter.dev)

Metric definition

ai_percent = sum(ai_accepted) / sum(git_diff_added_lines) over the window, the same ratio each uploaded commit summary already carries as ai_percent (upload_commit_authorship_summary in post_commit.rs).

• Window: the last 90 days of non-merge commits on the current branch by default; --since <date|duration> (anything git log --since accepts) or --all-time.
• Commits without an authorship note add nothing to either sum but are counted, so the output reports coverage (commits_with_authorship / commits), like RangeAuthorshipStatsData.
• Merge commits are skipped (they attest no lines and would only lower coverage).
• .autter-ignore and --ignore <pat> apply through effective_ignore_patterns, as in autter stats.
• The walk is capped at 2000 commits; the output says when the cap was hit (capped: true).

Computation lives in src/authorship/repo_share.rs; the command in src/commands/badge.rs.

Two snippet modes

1. Live badge (cloud-linked repo, signed in). POST /cli/repo-badge-link with { "repo_url" } returns { "token", "badge_url"?, "page_url"? } (ApiClient::create_repo_badge_link, mirroring upload_commit_authorship_summary). The snippet points at <api_base_url>/api/public/repos/<token>/badge.svg and links to the repo's Autter page. The lookup runs on a thread with a 5s recv_timeout, so it never blocks longer than that.
2. Static badge (everyone else). A shields.io static badge with the local number, plus one line saying why the live badge was not used. With --write on a GitHub remote the snippet becomes a shields.io endpoint?url= badge reading the committed .autter/badge.json from raw.githubusercontent.com, so it updates from the file.

--json prints the payload below, directly usable as a shields.io endpoint; --write [path] (default .autter/badge.json) stores it.

{"schemaVersion":1,"label":"AI-written","message":"72%","color":"5b5bd6","ai_percent":72.04,"ai_accepted":912,"added_lines":1266,"commits":58,"commits_with_authorship":54,"since":"2026-08-05","capped":false}

Colors (documented in autter badge --help): no data lightgrey; under 25% 74c0fc; 25-49% 007ec6; 50-74% 5b5bd6; 75% and up 2ee6c5 (Autter teal).

Backend half (separate monorepo change, not in this PR)

• POST /cli/repo-badge-link (authenticated, org-scoped) returning the token.
• GET /api/public/repos/:token/badge.svg: copy renderBadgeSvg from backend/src/services/scan-passport.ts and the token-gated route pattern /public/scans/:token/badge.svg from backend/src/routes/public-scans.ts. Data source: the commit_authorship_summaries table created in backend/src/routes/cli-data-plane.ts, aggregated per repo_url with the same ratio and color thresholds as above so both snippet modes match.

Tests

• tests/integration/badge.rs (explicit mock_ai / mock_known_human checkpoints): all-AI repo, mixed repo, commits lacking notes (coverage), .autter-ignore, window flags and empty window, --write default and custom path, GitHub-remote endpoint snippet, help text; insta snapshot of the no-cloud Markdown output.
• Unit tests for colors, message rounding, shields URL escaping, flag parsing, and percent.

cargo fmt --check, cargo clippy --all-targets -D warnings, and cargo test badge are clean locally.

🤖 Generated with Claude Code

---

^{Open in [code]smith · Need help on this PR? Tag @codesmith-bot with what you need.}

[sagnik11]

Closing: this code already shipped in autter 3.0.0 through #82, which merged this branch in. Every file here is identical on main.