How CONFIG.md evolved across versions.
Added a retrieval step that pulls the surrounding files and prior conventions before review, cutting false positives from missing context.
# CodePilot CR — Config (v2)
## Pipeline
1. Rule filters drop generated files, lockfiles, and vendored code
2. Retrieve surrounding files + prior conventions for each changed hunk
3. Model reviews hunks WITH that context
4. Synthesize inline comments
## Model
- Claude Sonnet
## Notes
- Repo-context retrieval sharply cut context-free false positives
Cheap rule-based filters drop noise, then the model reviews what is left.
# CodePilot CR — Config (v1)
## Pipeline
1. Rule filters drop generated files, lockfiles, and vendored code
2. Model reviews the remaining hunks
3. Synthesize inline comments
## Model
- Claude Sonnet
## Known issues
- No repo context: flags patterns that are fine given surrounding code
Diff CONFIG.md between any two captured versions — not just the latest change.
- # CodePilot CR — Config (v1)+ # CodePilot CR — Config (v2) ## Pipeline 1. Rule filters drop generated files, lockfiles, and vendored code- 2. Model reviews the remaining hunks- 3. Synthesize inline comments+ 2. Retrieve surrounding files + prior conventions for each changed hunk+ 3. Model reviews hunks WITH that context+ 4. Synthesize inline comments ## Model - Claude Sonnet - ## Known issues- - No repo context: flags patterns that are fine given surrounding code+ ## Notes+ - Repo-context retrieval sharply cut context-free false positives