pr-scope-verification

name	pr-scope-verification
description	Use when a user asks "verify PR #X covers Y; report gaps", "does PR #X implement feature Y?", or any scope/coverage verification request. Performs a read-only diff audit against the PR head and merge base, then emits a structured JSON gap report with explicit file:line citations for every gap. Trigger patterns include "verify PR covers X", "does PR cover Y", "audit PR against these requirements", "scope check for PR #X", and "does this PR actually fix X". This skill covers the audit pattern; it does NOT cover code quality review (use github-code-review) or PR lifecycle management (use github-pr-workflow).
category	github

PR Scope Verification

Read-only audit workflow for answering "does PR #X cover Y?" with citations. Never infer coverage from PR title, description, or branch name alone — always verify against the actual diff between the PR head and the merge base.

When to use

• "Verify PR #X covers Y; report gaps"
• "Does PR #X implement feature Y?"
• "Audit PR #X against this checklist"
• "Is claim Y covered by PR #X?"
• "Scope check for PR #X — does it actually address Z?"
• Any time the user wants explicit, citation-backed coverage flags

Workflow

1. Locate the worktree. Find the shared worktree (often /private/tmp/pr-cluster-wt-XXXX or similar). cd into it. Run git log -1 --format='%H%n%D%n%s' and git status -sb to confirm the worktree state. Note: the worktree may be detached (## HEAD (no branch)).

2. Resolve correct refs. Detached HEADs are common in shared worktrees. Use and (or whatever the actual target branch is) to get explicit SHA refs. Then enumerates commits, and gives the file-level change set.