← ClaudeAtlas

rechecklisted

Re-review a pull request after the author pushed fix commits, in any language or stack. Use this whenever someone asks to re-check, re-review, re-verify, or "look again" at a PR that already has review comments — `/recheck <PR>`, "cek ulang PR
zahidakhyar/skills · ★ 0 · AI & Automation · score 72
Install: claude install-skill zahidakhyar/skills
# Recheck A second pass over a PR that was already reviewed. The value here is narrow and specific: **deciding what the new commits actually changed about your earlier findings.** A fresh full review would re-derive things you already know and, worse, tends to soften prior findings that nobody actually fixed. First review → `/pr-review`. Argument: `/recheck <PR number|URL>`. Missing → list open PRs carrying a `reviewed:` marker of your own and ask which one. Needs `gh` (authenticated) and `jq`. The repo can be any language — gates are detected from the repo, never assumed from habit. Severity labels, body shape and comment style follow `${CLAUDE_SKILL_DIR}/../pr-review/references/review-protocol.md`; a repo `REVIEW.md` overrides it. **The one rule everything else serves:** a verdict comes from reading the post-fix code or from command output you paste into the report. Commit messages, PR descriptions, and author replies describe *intent*; they are evidence of what someone meant to do, not of what the code now does. Half the point of a recheck is catching the gap between the two. ## 1. Get the factual state ```bash "${CLAUDE_SKILL_DIR}/scripts/pr_state.sh" <PR> [repo-dir] ``` Returns one JSON object: `baseline`, `baseline_source`, `head`, `force_pushed`, `unchanged`, `commits[]`, `changed_files[]`. Three things it handles that are easy to get wrong by hand: - **Baseline** = the commit the last review saw. It prefers your own newest `reviewed: <sha>` marker (a teammate