review-evo

# ReviewEvo

A self-improving code reviewer. It analyzes your git history, identifies risk hotspots, learns your team's conventions, and builds a persistent knowledge base that sharpens every review.

**No external services. No API keys. No dependencies.** It uses git and the agent's built-in tools — nothing else.

**Follow these steps in order.** Complete each step fully before moving to the next.

## Prerequisites

Verify git is available:

- Run `git --version` and confirm output

The user must be inside a git repository with at least 20 commits of history. Run `git rev-list --count HEAD` to confirm. If fewer than 20 commits, warn the user that analysis will be limited but can still proceed.

## Step 1 — Detect Project and Load Prior Learnings

Check if this project has been reviewed before:

```
ls .review-evo/learnings.md 2>/dev/null
```

**If the file exists:** Read `.review-evo/learnings.md` in full. This contains findings from prior runs. Reference these throughout the review — confirm resolved issues, track recurring patterns, and build on previous analysis. Tell the user: "I found learnings from a previous review. I'll build on those."

**If the file does not exist:** This is a first run. Tell the user you'll create the knowledge base after analysis.

Then detect the project setup by checking for these files in the repo root:

- `tsconfig.json` → TypeScript
- `package.json` → Node.js (read `scripts` for build/test/lint commands)
- `requirements.txt` or `pyproject.toml` → Python
- `go.mod` → Go
- `Cargo.toml` → Rust
- `pom.xml` or `build.gradle` → Java

Report what you found and confirm with the user.

## Step 2 — Analyze Git History

Run each of these commands and capture the output. Do not summarize prematurely — collect all data before drawing conclusions.

**Recent activity (last 50 commits):**
```
git log --oneline -50
```

**Contributor breakdown:**
```
git log --since="6 months ago" --format="%an" | sort | uniq -c | sort -rn
```

**High-churn files (...