← ClaudeAtlas

review-correctnesslisted

Review code for bugs, incorrect state transitions, races, and failure handling, including closed-world branching, unknown external values, swallowed errors, masking defaults, invariants, deadlines, cancellation, and retry safety. Use for "review correctness", "review logic", "review defensive", "check exhaustiveness", "fail fast review", or "robustness review".
nielsmadan/skills · ★ 1 · Code & Development · score 77
Install: claude install-skill nielsmadan/skills
<!-- Generated from https://github.com/nielsmadan/agentic-coding — edits here are overwritten. --> # Review Correctness Check correct behavior under normal inputs, failures, and changing assumptions. Perform both passes below; a general bug scan does not replace the failure-path checklist. Read `references/defensive-checklist.md` for examples, language-specific exhaustiveness mechanisms, and supporting sources when a finding needs them. Follow this skill's ownership and evidence rules when using those examples. ## Review grading Use only these finding priorities, in descending order: - **Critical Issues (Must Fix):** a verified path causes data loss, a security failure, a materially wrong operation, or makes a core workflow unusable without reasonable recovery. - **Improvements (Should Fix):** an ordinary supported workflow demonstrably fails or repeatedly imposes substantial friction, or a concrete design defect creates meaningful maintenance cost. - **Suggestions (Nice to Have):** a worthwhile improvement with small practical impact, including optional polish, local simplification, and rare recoverable edge cases. Grade the demonstrated consequence, realistic reachability, and available recovery against project priorities. A category, missing convention, hypothetical future problem, or confidence that a claim is true does not set its priority. Do not assign automatic severity floors or ceilings. Keep unverified claims in validation gaps, outside the graded find