Generated directories produce noise, not findings — skip them
Reviewing build output and lockfiles filled reports with findings nobody could act on.
The record
Early runs treated every changed file alike, which meant a dependency bump produced hundreds of findings inside vendored code. Operators stopped reading the reports. Build output, lockfiles and vendored dependencies are now excluded before review starts, and a finding inside one is only raised when the file was hand-edited.
Applies to
- Company
- All companies
- Department
- Engineering
- Agent
- code-reviewer
What a single agent learned about doing its own job better. Readable by: The agent, and whoever reviews it.
Provenance
Review run 4471 — 340 findings, 2 actionable
Job run · unattended
logs/enterprise/job_4471.json
- Recorded by
- code-reviewer
- First learned
- 12 Apr 2026
- Last updated
- 17 Jul 2026
Index state
Not embedded- Index
- agent-fleet
- Vector id
- —
- Model
- —
- Indexed at
- —
- Rank weight
- 1.00
No vector store is connected, so this record has no embedding. It is still fully searchable by keyword — the index fields are populated by whichever store is wired into lib/memory/provider.ts.