If you’ve ever opened a legacy project and felt your soul briefly leave your body, this one’s for you.
You know the scene:
- 200k+ lines of code
- Three architectural “eras” living in the same repo
- Tests that pass… somehow
- A PR review queue that feels like airport security
Let’s fix that.
This post is a practical, hands-on guide to using gemini-cli as a serious productivity multiplier — not as a gimmick, not as a toy, but as a real engineering tool you can plug into your daily workflow today. Btw, I’m not ‘with’ Google for many years now… so it’s all my personal thoughts.
By the end, you’ll know exactly how to:
- Explore massive codebases without losing your mind
- Refactor safely and confidently
- Pre-review your own PRs
- Generate useful tests (not garbage)
- Debug failures faster
- Automate repetitive dev work