skills

Use when asked to audit a repository's health, assess technical debt, evaluate codebase quality end-to-end, or produce a prioritized improvement plan — including "how bad is this code", new-team-takeover or pre-acquisition reviews, and periodic engineering health checks. Analysis-only; never modifies code.

Use when the user asks to create, update, or refresh a production runbook, ops guide, or incident response documentation for a deployed application — audits actual infrastructure config to generate reality-based operations documentation