Hey HN,
I've been building Context42 to solve a problem that's been bugging me: getting AI to write code like me, and helping disseminate coding best practices.
The core insight is simple - your existing code is already your best style guide. Instead of debating tabs vs spaces or where to put your curly braces, Context42 analyzes your actual codebase and generates comprehensive style documentation using Google's Gemini AI.
Here's what makes it special:
1. *Language-aware analysis* - It groups files by language and generates specific style guides for each. Your TypeScript patterns won't bleed into your Python conventions.
2. *Dependency-smart processing* - It analyzes child directories before parents, building up context as it goes. This means it understands your module structure and can identify patterns that emerge across your architecture.
3. *Built for real codebases* - With configurable concurrency, resume capability, and automatic cleanup, it's designed to handle everything from small projects to massive monorepos. The terminal UI (built with Ink/React) gives you real-time progress on what's happening.
4. *Pragmatic over prescriptive* - Instead of enforcing arbitrary rules, it documents what you're already doing. This makes it easier to onboard new developers and maintain consistency without religious debates.
The technical approach is interesting too - it uses a worker pool pattern with abort controllers for graceful shutdown, SQLite for persistence (so you can resume failed runs), and a file registry system that guarantees cleanup even on crashes.
I built this because I believe the best documentation is the kind that reflects reality, not aspirations. Your code style isn't what you think it should be - it's what it actually is. And that's worth documenting.
You can check it out at: https://github.com/zenbase-ai/context42
Would love to hear your thoughts, especially if you've tackled similar problems in your teams. What's worked for you in maintaining code consistency at scale?
