← ClaudeAtlas

sol-simplify-reviewlisted

The default protocol for any merge-gate or pre-merge review: inventory the reviewed head once, exhaustively, then verify only closure and remediation regressions. Use whenever a change is about to be merged and someone is reviewing it — not only when asked for it by name, and not only when rounds have already gone badly. Writing a fresh ad-hoc review prompt for a merge is the failure this replaces, and it happens most under time pressure or when a usual reviewing model is unavailable: swap the model inside this protocol rather than abandoning it. Skip only for an ordinary small one-pass read where nothing merges.
MongLong0214/sol-simplify · ★ 2 · Code & Development · score 78
Install: claude install-skill MongLong0214/sol-simplify
# sol-simplify review Review the product once. Freeze what must be true. Verify the repair once. A sequence of valid findings is still a failed review process when each pass selects another surface from the same finite change. Round 1 must enumerate that surface. Round 2 must close it, not rediscover it. `sol-simplify: the inventory prevents repeated class-local fixes; remove it when the change is merged or abandoned.` ## Reach for this by default If a change is about to merge and someone is reviewing it, this is the protocol. That includes the cases where it is least convenient: a deadline, an outage of the model you normally review with, a PR you have already reviewed several times, a change you believe you understand. Those are the moments an ad-hoc review prompt gets written instead, and an ad-hoc prompt samples findings rather than bounding them — which is the whole reason this exists. A model being unavailable changes who executes the round; it does not change the round. Switching to it late is cheap. A reviewer that has already read the code can produce the round-1 inventory as a change of output shape, not a restart. ## Why this is not a registry The inventory is one reviewer-owned artifact for one PR head. It is not committed to the product repository or updated after every merge. Its obligations expire with the PR; the host may retain sealed round receipts for retrospective measurement. Every item names product behavior, a security boundary, or an explicit