Archexa: A CLI That Turns Codebases Into Architecture Docs, Impact Analysis, and Reviews

Built this while working across multiple microservice codebases — would love feedback from folks solving similar problems. The Problem Architecture documentation tends to drift over time. It’s usually written once, when the system is simpler. But as the code evolves — refactors, new services, changing APIs, updated data flows — the documentation doesn’t keep up. Updating architecture docs is not trivial. It often requires re-understanding the system end-to-end, tracing dependencies, and reconstructing how components interact. In practice, this rarely happens alongside regular development work. Over time, this creates familiar challenges: New engineers take longer to ramp up “Safe” changes can impact downstream systems unexpectedly Code reviews focus on diffs, not system-wide effects Important system knowledge lives in people’s heads The architecture knowledge does exist — it’s all in the code. But it’s distributed across many files and not easily accessible as a whole. What I Built: Ar