17,841 Lines Changed. 3 Things You Actually Need to Look At. A developer released Lenscheck, a deterministic semantic pull-request reviewer for Python web apps (Django/Django REST Framework) that parses code with Python's standard library rather than an LLM. The tool converts a diff into a ranked set of findings and a flow graph tracing route, auth, database tables, external calls, cache, async and PII, and can discover, confirm and enforce codebase-specific rules on every PR; on a real 17,841-line PR it surfaced three items to review. It ships as a zero-dependency pip package with a GitHub Action and a local web UI, and never runs the reviewed code. Git shows you what lines changed. Lenscheck shows you what they mean , where to look, and whether they broke a rule. It's a semantic PR reviewer for Python web apps. This guide starts from zero — every idea, command, and setting in plain English — then shows you how to set Lenscheck up once and run it across all your repos personal, team, or organization . No LLM · Deterministic · Never runs your code · Nothing leaves your network Try it on a repo you already have — see the review right in your terminal: pip install lenscheck-semantic-reviewer cd your-django-repo lenscheck review your current branch vs. main → the few things that actually matter Turn it on for a team — one command drops a GitHub Action that reviews every PR, advisory only : lenscheck init writes .github/workflows/lenscheck.yml comments, never blocks git add .github/workflows/lenscheck.yml && git commit -m "add lenscheck" && git push Prefer to click around? lenscheck serve opens a local web UI with the flow graph. That's the whole tool: a flow graph of what a PR does, and rules it can enforce. Everything below is depth for when you want it. When you open a Pull Request PR , the reviewer sees a diff — red lines removed, green lines added. But a diff tells you what text changed , not what it means . Did this PR add a new way into your app? Did it start writing to your database without a login check? Did someone's email address just start leaving your server? Lenscheck reads your PR and tells you what it means — in a few high-signal findings, each pointing at the exact line to look at. It's built for Python web apps Django / Django REST Framework today . It is not an AI that guesses. It reads your code with Python's own parser and reports facts . When it isn't sure, it says so you'll see a ⚠ . It never dresses up "I didn't see it" as "it's safe." Lenscheck has a lot of features, but they exist to serve two that matter most. If you remember nothing else from this guide, remember these two. The problem. A git diff shows you text — hundreds of red and green lines. It doesn't tell you that one of them opened a new endpoint, started writing to the database, or sent a user's email out of the building. On a big often AI-generated PR, the reviewer skims — and the risky change ships. What Lenscheck does. It reads the code before and after the PR and turns the diff into meaning : what changed → how it flows → where to look . A huge diff becomes a short, ranked list plus a flow graph of each change route → auth → DB tables → external → cache → async → PII . On a real 17,841-line PR, that came out to 3 things to look at. Git tells you what lines changed. Lenscheck tells you what those changes mean . The problem. Every codebase has rules everyone "knows" — auth before any DB write , personal data never leaves without a login — but nothing actually enforces them. A PR quietly breaks one, and What Lenscheck does. It discovers those rules from your git history, lets you confirm the real ones, then enforces them on every PR — flagging and optionally blocking a new violation while ignoring existing debt. This is the part that compounds: over time Lenscheck learns the rules your codebase cares about, and no competitor has that knowledge. Everything else is in service of these two. Intent-vs-behaviour contradictions, traced PII leaks, dependency-capability scanning, SARIF, inline comments, labels, the org roll-up — all of it makes the two features above sharper. The rest of this guide explains each one, but if the list ever feels like a lot: it's a flow graph and enforced rules . That's the product. pip install lenscheck-semantic-reviewer That's it — Lenscheck has zero dependencies it only uses Python's standard library . You now have a lenscheck command. Check it: lenscheck --help Lenscheck Semantic Reviewer Usage: lenscheck