exact-head-review
Resolve the live PR head and verify an isolated checkout before reviewing or recording an exact-revision verdict.
SKILL.mdskills/exact-head-review/SKILL.md
GitHubReview the actual pull-request head
A supplied SHA is a claim. Resolve the current head independently through the repository API or gh pr view --json headRefOid,baseRefOid,state. Confirm repository identity and open state. Compare full object IDs, never short prefixes.
- Record the resolved head and base, repository, PR number and retrieval time.
- Fetch the PR's ref through the verified repository remote. Check command success, then verify the fetched object equals the API head. Stop on mismatch or unavailable evidence; do not use stale
FETCH_HEAD. - Create a new detached worktree at that exact commit in an operator-chosen review directory. Do not reuse, reset or clean another worktree. Confirm both HEAD and clean tracked/untracked state before testing.
- Read the actual diff and consumers. A nonempty diff does not prove the behavior is wanted; a test count does not prove a guard can fail. Use
mutation-checkfor important negative paths. - Re-read live head/base before issuing the verdict. If either changed, identify affected evidence and review the new candidate. Do not transfer approval by branch name.
- Report full revision, findings, executed checks, limits and whether the verdict is current. Remove only your clean disposable worktree with
git worktree remove; preserve dirty evidence for inspection.
No script is bundled for this workflow. Use the available repository connector or installed Git/GitHub CLI, and report unavailable dependencies explicitly.