✓
Changed-file first
Keep everyday review fast. Run full scans when you need an audit or baseline.
Nice CodeReview code with evidence.
Lightweight guardrails for recurring engineering mistakes — local, agent-friendly, and CI-ready.
Skip to content
Public guidance
Patterns + sources
Custom checks + native tools
Local, commit, or CI review
$ nice-code --changed --project .
PASS 0 new findings · 18 files checked
REVIEW AP-ASYNC-001 src/load.ts:42 · verify independent awaits
A practical review layer
Nice Code catches recurring issues that deserve engineering judgment: missing operational context, suspicious async work, weak error handling, unsafe persistence changes, secret exposure, and unsupported performance claims.
It complements compilers, formatters, linters, tests, and tools such as SonarQube. It does not replace them, and a text-based check cannot prove an architectural decision by itself.
Choose a starting path
| If you are… | Start here |
|---|---|
| Trying Nice Code in a repository | Getting started |
| Adding it to a project | Project integration |
| Wiring it to an agent | Agent integration |
| Adding it to CI | CI |
| Reviewing scan output | Findings and statuses |
| Improving the patterns | Pattern lifecycle |
Use the smallest check that answers the current question. Changed-file checks are the default; full scans, baselines, metrics, and monthly audits are explicit tools for understanding change over time.