⚡SkillingMain
🛒Sign inGet started

Code Review Checklist

$1.99Official

Use when reviewing a diff, PR, or staged changes: a five-pass protocol that yields severity-ranked findings with concrete failure cases.

code-qualitycode-reviewqualitypull-requestscorrectnesssecurityseverity· by SkillingMain

What you get

  • ✓7-step procedure
  • ✓1 ready-to-run code block
  • ✓7-point quality checklist
  • ✓8 pitfalls to avoid
  • ✓Installs into 6 tools
Version
v1 →
Last updated
today
Length
6 min read
Requires
Works with any modern AI assistant

Works in: Claude Code, Codex, Cline, opencode, OpenClaw, Hermes

Preview

When to use

Use when asked to review a pull request, diff, patch, commit range, or staged changes — or when the user says "review this", "check my changes", or "is this ready to merge". Do not use for auditing an entire codebase from scratch (that is an audit, not a review) or for pure style disputes a formatter can settle.

Inputs to gather

  • The diff itself: git diff main...HEAD (or the PR diff), plus git diff --stat main...HEAD for shape and size.
  • Stated intent: PR description, linked issue, or the user's one-line summary of what the change is supposed to do. If none exists, ask — you cannot judge correctness without knowing intent.
  • Surrounding context: for each modified f

…

🔒 Buy once ($1.99) to unlock the full playbook, download it, and install it in every tool you use.