Everything you need to know about CleanLens
In-depth technical documentation for every part of the project: how it works, the rules, scoring, configuration, and how to tune it for your team.
11 Customization guide
How to tune CleanLens for your team: recipes for strictness, noise, scoring, identities, history, CI
Start here
2 docsHow it works
7 docsArchitecture
Layers, module map, the 7-step pipeline, data flow between modules
Read04Git layer
Repository checks, commit listing, diffs, blob reading, developer identity merging
Read05Analyzers
File scanning, glob matching, the JS/TS and Python analyzers, duplicate detection, secret and name heuristics
Read06Rules reference
Every one of the 14 rules in depth: exact detection logic, options, false-positive notes
Read07Attribution engine
Commit replay, fingerprints, attribution status and confidence
Read08Scoring
The Clean Code Score formula, Bayesian shrinkage, confidence levels, ranking, worked example
Read09Caching & performance
The per-commit cache, invalidation, concurrency, speed tips
ReadUsing & configuring
5 docsConfiguration reference
Every key in .clean-code-tracker.json, the local override file, VS Code settings, CLI flags, and which one wins
Customization guide
How to tune CleanLens for your team: recipes for strictness, noise, scoring, identities, history, CI
Read12VS Code extension
Commands, sidebar views, dashboard, inline diagnostics
Read13CLI
Every flag, output formats, exit codes, CI and pre-commit integration
Read14Report schema
The JSON ProjectReport produced by --json, field by field