thalarch-reviewlisted

Runs risk-sized, evidence-first review of code changes. Use before completion, PR creation, or after meaningful implementation. Separates requirement compliance from engineering quality, uses independent reviewer contexts and perspective shifts to break self-review blind spots, confirms findings before fixing them, and supports lite, standard, and deep review depth.
LUC4N3X/antigravity-thalarch · ★ 2 · Code & Development · score 65

Install: claude install-skill LUC4N3X/antigravity-thalarch

# Thalarch Review Review exists to find **real** defects and risk, not to manufacture criticism. ## 1. Review depth ### Lite Small/low-risk diff: one independent general reviewer. ### Standard Meaningful code change: - requirement/spec compliance; - correctness/regression/maintainability. ### Deep Add only the lenses justified by the changed surface: - security; - performance/concurrency; - persistence/data; - API/compatibility; - language/platform specialist; - UI/design/vision; - CI/release. Do not invoke a council for ceremonial thoroughness. ## 2. Lens — specification compliance For every acceptance item mark: - `PASS`; - `FAIL`; - `UNVERIFIED`; - `OUT OF SCOPE`. Check for missing behavior and unrequested changes. ## 3. Lens — correctness/regression Inspect as relevant: - lifecycle/state ownership; - boundaries and edge cases; - async/concurrency/cancellation; - resource cleanup; - persistence/migrations; - network timeout/retry/idempotency; - API/ABI/wire compatibility; - dependency/version assumptions; - test validity; - consumer/caller behavior. ## 4. Blind-spot breakers When the reviewer may share the author's mental model, deliberately change perspective. Use only what helps the current diff. ### Contract-before-body For an important changed function/class/interface, state its expected contract **before** reading the implementation in detail. Then compare implementation to that contract. ### Consumer-first Inspect at least one real caller/cons