This is the architecture review you run before tech debt becomes a rewrite. It scans for the structural problems that compound over time: monolithic files over 500 lines, error handling that silently swallows failures, type safety shortcuts like unchecked casts, and gaps between your test coverage and actual critical paths. It also checks LLM-friendliness, which matters more than you'd think when half your team is pair programming with Claude. The focus is macro over micro, so it won't nag you about formatting but will tell you exactly which 1200-line file needs to be split into what. Best used quarterly or when onboarding makes you realize nobody understands the architecture anymore.
npx skills add https://github.com/getsentry/warden --skill architecture-review