From Stack Trace to Root Cause - Archexa's New Diagnose Command

Archexa's new diagnose command correlates errors with actual source code to find the root cause, not just the symptom. Archexa v0.2.1-beta. Apache 2.0 license. Single binary — macOS, Linux, Windows. GitHub: github.com/ereshzealous/archexa A stack trace tells you where your code failed. It doesn't tell you why . NullPointerException at UserService.java:42 is the symptom. The root cause is three files upstream — a repository method that returns null instead of Optional, called by a service that doesn't check for it, triggered by a controller that passes through an unvalidated ID. Finding that chain takes time. You read the failing line. You find the caller. You read the caller. You check what data it passed. You follow that data to where it originated. You do this across 3, 5, sometimes 10 files until you find the actual bug. Most developers paste the stack trace into ChatGPT. It gives a plausible-sounding answer — but it doesn't have your code. It guesses based on the error message. It