I've been frustrated reviewing large PRs where I can't tell what changes actually matter or hopping back and forth between files during review. I built Tracer to explore what an "intelligent git diff" might look like. Curious if anyone else is thinking in this direction.
What it does:
- Model sorts files by impact (breaking changes first, then features, fixes, etc.)
- 4 navigation modes: file-level, hunk-level, intelligent, and linear
- React-based TUI with syntax highlighting for 19 languages
- Press Enter on any line to jump to your editor at that exact spot
This is extremely early (v0.0.1) and I'd love feedback on:
1. Does the "sort by impact, not file path" idea resonate with anyone?
2. What other ways would you want diffs sorted / filtered?
3. Are there UI/navigation patterns I'm missing entirely?
Would love to know if anyone else has been thinking about this problem or if there's prior work I should look at.
I've been frustrated reviewing large PRs where I can't tell what changes actually matter or hopping back and forth between files during review. I built Tracer to explore what an "intelligent git diff" might look like. Curious if anyone else is thinking in this direction.
What it does: - Model sorts files by impact (breaking changes first, then features, fixes, etc.) - 4 navigation modes: file-level, hunk-level, intelligent, and linear - React-based TUI with syntax highlighting for 19 languages - Press Enter on any line to jump to your editor at that exact spot
This is extremely early (v0.0.1) and I'd love feedback on: 1. Does the "sort by impact, not file path" idea resonate with anyone? 2. What other ways would you want diffs sorted / filtered? 3. Are there UI/navigation patterns I'm missing entirely?
Would love to know if anyone else has been thinking about this problem or if there's prior work I should look at.
Try it: bunx @cs50victor/tracer
GitHub: https://github.com/cs50victor/tracer