Codebase intelligence for AI and humans: code health scores, auto-generated docs, git analytics, dead code detection, and architectural decisions via MCP.
Python aicode-complexitycode-healthcode-intelligencecode-qualitydead-codedeveloper-toolsdocumentationgit-analyticsmcpopen-sourcepythonrefactoringstatic-analysistechnical-debt
Change-Risk Example
Rank a commit or base..head range against recent repository changes with
repowise risk. No LLM key required — pure git + calibrated signals.
Works without repowise init (index is optional).
Prerequisites
- A git repository with at least one commit.
repowiseonPATH(uv tool install repowiseor from this repo:uv sync --all-packages).
cd /path/to/your-repo
1. Score your current change, a commit, or a range
repowise risk # score uncommitted work, else HEAD
repowise risk HEAD # score the last commit
repowise risk main..HEAD # whole branch / PR as one change
repowise risk HEAD~5..HEAD # recent local work
The headline is size and spread: the change's percentile among this repo's recent commits by diff size, not a bug predictor. Below it, the fix history: which of the touched files have needed bug fixes before, recency-weighted. Then the 0–10 score, which measures how large and spread out the change is rather than how dangerous.
2. Narrow what counts
# Only certain suffixes
repowise risk --ext .py
repowise risk main..HEAD --ext .ts,.tsx
# Omit paths (repeatable); root .riskignore also applies
repowise risk main..HEAD -x 'tests/' -x '*.spec.ts'
3. Machine-readable output
repowise risk main..HEAD --format json
Smoke checklist
| Step | Expected |
|---|---|
repowise risk |
Table led by the size-and-spread percentile, with a supporting diff-shape score |
repowise risk main..HEAD |
Same shape for the range (or a clear revspec error) |
repowise risk --format json |
JSON object; no API key needed |