Loupe代码助手影响力测量工具

Install

macOS and Linux (recommended):

brew install stephanschmidt/tap/loupe

The Homebrew tap publishes a fresh bottle on every release, Intel and Apple Silicon.

<details> <summary>Other install methods</summary>

- Go: go install github.com/StephanSchmidt/loupe/cmd/loupe@latest - Prebuilt binaries for linux / macOS / windows on amd64 + arm64: see the releases page - From source:

  git clone https://github.com/StephanSchmidt/loupe.git
  cd loupe
  make build        # produces ./bin/loupe
  

</details>

Usage

loupe init        # interactive wizard, writes loupe.yaml
loupe baseline    # ingest, then render the deck
loupe present     # opens the latest deck in your browser
loupe status      # local sqlite summary, no API calls

loupe baseline prompts for credentials every time it runs (echo off). There are no env vars or keychain hooks in v0 — I'd rather not invent a key-management story before it's needed. State lives at .loupe/state.db; decks go under ./reports/<timestamp>/.

If you only care about one repo on a GitHub account that has fifty others, narrow it down:

loupe baseline --repo StephanSchmidt/loupe

--repo filters the git host before any API call. When both providers are GitHub, the tracker filter follows automatically. Use --project KEY to scope the tracker side independently (a Jira project key, for instance).

Each run also drops standalone chart exports under ./reports/<timestamp>/charts/:

• throughput.png, adoption.png for Slack and email
• throughput.svg, adoption.svg for board docs and wikis

The in-browser deck uses Apache ECharts; the PNG/SVG files are static snapshots produced server-side.

Config

loupe.yaml holds non-secret coordinates only. Full shape is in loupe.example.yaml:

org: acme-eng

git_host:
  provider: bitbucket-cloud
  base_url: https://api.bitbucket.org/2.0
  username: you@example.com

tracker:
  provider: jira-cloud
  site: acme.atlassian.net
  email: you@example.com

ai_adoption:
  # cutover_date: 2026-03-15   # uncomment to pin the cutover yourself
  detection:
    co_author_trailers: true
  min_weekly_commits_for_cutover: 0.05

windows:
  baseline_weeks: 12
  comparison_weeks: 12

output:
  path: ./reports

Every workspace and Jira project the credentials can see is indexed. There's no include/exclude list — let me know if you actually need one.

For GitHub-only setups, set both providers to github and supply a PAT at prompt time:

git_host:
  provider: github
  # base_url and username are optional; defaults to api.github.com / authed user

tracker:
  provider: github
  # base_url is optional; defaults to api.github.com

Loupe enumerates your own repos plus every org you belong to, and treats each repo with Issues enabled as a tracker project.

For GitLab-only setups (cloud or self-hosted), point both providers at gitlab and set base_url to your instance — one PAT covers both:

git_host:
  provider: gitlab
  base_url: https://gitlab.com           # or https://gitlab.acme.com

tracker:
  provider: gitlab
  base_url: https://gitlab.com           # match git_host

Loupe walks every group the token can see (subgroups included), and treats each project as both a repo and a tracker project. Issue/merge-request filters use path_with_namespace (e.g. acme/team/svc).

For Azure DevOps (cloud or Server), set both providers to azuredevops and supply the org name via git_host.username:

git_host:
  provider: azuredevops
  base_url: https://dev.azure.com          # or https://devops.acme.com/tfs
  username: myorg                          # Azure organization name

tracker:
  provider: azuredevops
  base_url: https://dev.azure.com
  # site is optional when git_host is also azuredevops; otherwise set
  # site: myorg

Workspaces map to Team Projects, repos to Azure Git repositories, and tracker projects to the same team projects (work items are queried via WIQL).

For Linear as a tracker (mix-and-match with any git host), set:

tracker:
  provider: linear
  base_url: https://api.linear.app
  # project keys are Linear team keys, e.g. "ENG"