Post by Ashish Gupta

Your repository already knows where the next outage will happen. Excavate just surfaces it. It just hit 1000+ downloads within a week!!! Shipped a big update to Excavate recently - a CLI that analyses Git history to surface architectural risk, ownership gaps, and long-term maintainability issues hiding inside repositories. Some of the things shipped recently in Excavate: • 𝐋𝐋𝐌-𝐠𝐞𝐧𝐞𝐫𝐚𝐭𝐞𝐝 𝐢𝐦𝐩𝐫𝐨𝐯𝐞𝐦𝐞𝐧𝐭 𝐩𝐫𝐨𝐦𝐩𝐭𝐬 𝐟𝐫𝐨𝐦 𝐫𝐞𝐩𝐨 𝐡𝐢𝐬𝐭𝐨𝐫𝐲 • Debt archetypes per file (time bomb, load-bearing wall, spaghetti, black box, fossil, ghost…) • Temporal coupling detection (files that repeatedly change together) • Orphan file + dead export detection • Knowledge cliff + survival metrics • Plain-English repo narratives via --𝘯𝘢𝘳𝘳𝘢𝘵𝘪𝘷𝘦 One thing that became very obvious while building this: Git history exposes architectural stress signals surprisingly well. You can often identify unstable boundaries, ownership bottlenecks, hidden coupling, or “future outage files” long before they become production incidents. Still early, but excited about where this goes. Would love feedback from people who obsess over codebase health, scaling engineering teams, or developer tooling. 𝘯𝘱𝘹 𝘦𝘹𝘤𝘢𝘷𝘢𝘵𝘦 https://tryexcavate.com/ https://lnkd.in/dcGxAydz GitHub Sourcegraph Linear Cursor CodeAnt AI Windsurf  #DeveloperTools #SoftwareEngineering  #BuildInPublic  #GitHub  #Engineering  #DevTools  #CodeQuality  #TechDebt  #Architecture  #AIEngineering  #OpenSource  #Programming  #DeveloperExperience  #DX #LLM  #CodeReview Ashish Gupta