verify-pr

Task: Verify Pull Request Claims

PR to verify: $ARGUMENTS

Purpose: Verify that a PR's description, commits, and plan match actual implementation.

Core 4 Foundation:

• Context: PR metadata + git changes + plan documents
• Model: Semantic verification capabilities
• Prompt: This systematic verification process
• Tools: Git commands, gh CLI, file operations

---

Instructions

You are verifying a pull request. Check that claims in PR description, commits, and plans match actual code changes.

Core Principles

1. Evidence before claims: Never mark verified without git command output proving it
2. Verify behavior, not names: Check what code DOES. Different filenames can provide same functionality.
3. Counter-evidence first: Define what would disprove claim BEFORE checking
4. Cross-reference patterns: If comparing implementations, check what feature IS first

---

Step 1: Identify PR and Extract Claims

Determine PR Type

The argument could be:

• Branch name: cursor/implement-plan-from-cu-plan-md-11ba
• PR number: #7 or 7
• Comparison: main...feature-branch

Commands to identify:

# If branch name given, check if it exists
git show-ref --verify refs/heads/$ARGUMENTS 2>/dev/null || git show-ref --verify refs/remotes/origin/$ARGUMENTS

# If looks like PR number, try gh
gh pr view $ARGUMENTS 2>/dev/null

# Get comparison syntax
git log --oneline main...$ARGUMENTS | head -10

Extract Claims

From PR description (if available):

gh pr view $ARGUMENTS --json body -q .body

From commit messages:

git log --format="%s%n%b" main...$ARGUMENTS

From referenced plan documents:

# Look for plan references in commits or PR description
git log main...$ARGUMENTS | grep -i "plan\|spec\|requirement"

Common claim patterns to extract:

• "Adds feature X"
• "Fixes bug Y"
• "Implements Z from plan"
• "Includes tests"
• "Updates documentation"
• "Breaking change"
• "Closes #123"