What problem does it solve? After you build a feature yourself, self-review is biased and shallow. This Skill runs an adversarial, independent audit over your branch diff: specialist review agents challenge the code from lenses that never saw you write it, and every runtime claim must be reproduced by execution before it counts as a finding. ## Core Features & Use Cases - Multi-lens parallel review: Semantic, guidelines, test-integrity, concurrency, and performance lenses run per language, each owning its files while seeing the rest of the diff as context. - Evidence-based refutation: Runtime findings must be reproduced with a failing test, race run, benchmark, or direct invocation; quality findings must cite a rule at a specific line, or they are dropped. - Ranked, re-graded report: Surviving findings are re-graded against one severity rubric, deduplicated before refutation, and reported with confidence levels and coverage gaps. - Use Case: After finishing a green feature branch, run clerk audit run --base main --brief "..." --request "..." to get a JSON report of confirmed defects before merging. ## Quick Start Ask the assistant to audit the current branch against main with clerk audit run, passing a brief and the original request verbatim.