Use when verifying documentation accuracy against the codebase, finding stale or missing docs, detecting incorrect behavior descriptions, or applying documentation improvements.
Use when auditing a codebase for architectural violations, dependency rule breaches, layer boundary violations, or pattern inconsistencies.
Use when creating a new hostile audit skill for this repository. Scaffolds the correct directory structure, frontmatter, and required sections.
Use when you need to identify which architectural patterns a codebase uses, understand its structural boundaries, or generate an architecture profile before auditing.
Use when asked to review code, find bugs, audit for correctness, stress-test a PR, or when someone says "tear this apart" or "what's wrong with this".
Use when performing a comprehensive repository audit, reviewing code before a release, checking a PR for all bugs and defects, or when asked to "review the whole codebase", "audit…