← ClaudeAtlas

code-reviewlisted

Review an implementation slice against the actual diff, approved design and delivery packages, tests, and validation evidence, then record findings or a clean first-pass review. Use after implement hands off a milestone or when implementation review is requested. Use design-review, delivery-review, verify, or pr for those gates instead.
xiongxianfei/rigorloop · ★ 3 · Code & Development · score 80
Install: claude install-skill xiongxianfei/rigorloop
# Independent implementation review ## Test criteria application When the project explicitly adopts Test-model criteria, use the selectively loaded guidance below for test quality and maintenance. These criteria replace source-local shared test-purpose, case-selection and maintenance criteria for adopted work; retain specialist methods and historical procedures. Actual judgments, evidence applicability and closeout consequences remain with the responsible assessors under the project's review policy. ## Quick operating guide Use this skill to: inspect the actual review surface against its governing contract and record a first-pass review outcome. Read first: the actual diff, tracked governing authority, current milestone, relevant tests, and validation evidence. Produce: a recorded review status, findings or no-finding rationale, checklist coverage, and milestone-aware handoff. Stop when: authority, evidence, or milestone state cannot support a credible outcome, or an owner decision is required. Do not claim: branch-ready, PR-ready, verification passed, CI passed, or fixes owned by another stage. Next stage: review-resolution for findings, the next milestone after a clean non-final review, or final closeout after the required final holistic review. Use broader-section or full-file reading when bounded evidence is insufficient. ## Review and Closeout application When project authority explicitly adopts Review and Closeout policy, use the packaged application below f