code-audit

Analyze git history and report breaking changes in REST APIs. Use when the user asks to "find breaking API changes", "check for breaking REST changes", "what endpoints did I break", "is this a breaking change", "compare API versions", "what changed in the API", or anything about REST endpoint compatibility. Works for Flask, FastAPI, Express, Spring Boot, and OpenAPI/Swagger specs. Handles multi-file routers, shared request/response schemas, auth changes, and path prefix changes. Reads git history — no external tools required. TRIGGER this skill whenever the user mentions REST APIs, endpoints, routes, or API versioning alongside words like "breaking", "changed", "removed", "compatible", or "diff".

Find unused code — functions, classes, variables, imports, constants, types, and more. Use when the user asks to "find dead code", "find unused code", "clean up unused imports", "find unreachable code", or "find what can be deleted". Accounts for dependency injection frameworks (Spring, CDI, NestJS, Angular, etc.) to avoid false positives.

Audit and improve logging quality across a codebase. Use when the user asks to "improve logging", "fix log levels", "add logging", "review our logs", "make logging consistent", "we have bad logging", or anything about log messages being unclear, missing, or at the wrong severity. Produces a prioritized list of recommendations — does not edit files directly.