3-verify-pr-fix

# Verify a Candidate PR Actually Fixes the Issue Goal: take a PR number, check it out cleanly, re-run the same tool call that failed on `main`, compare the outputs, and produce a verdict — "fixes", "fixes but with concerns", "does not fix", or "cannot run". Pair with `/2-repro-issue` (which produces the baseline). No edits, no merges, no pushes. ## Phase 1 — Resolve the PR and its linked issue ```bash # Accept "498", "#498", or "https://github.com/.../pull/498" — extract the digits only PR=$(echo "$ARGUMENTS" | sed -E 's|.*/||; s|#||g' | grep -oE '^[0-9]+' | head -1) [ -z "$PR" ] && { echo "Invalid input: '$ARGUMENTS'. Pass a PR number or URL." >&2; exit 1; } REPO=stickerdaniel/linkedin-mcp-server gh pr view $PR --repo $REPO --json title,body,baseRefName,headRefName,headRepositoryOwner,mergeable,mergeStateStatus,additions,deletions,changedFiles,maintainerCanModify,statusCheckRollup ``` Extract the **linked issue number** from the PR body (`Closes #`, `Fixes #`, `Resolves #`, or plain `#N`). Call it `ISSUE`. If multiple, ask the user which one is the verification target. ## Phase 2 — Pick up the baseline + request metadata `/2-repro-issue` writes two files for each issue: - `/tmp/repro-issue-<ISSUE>-main.json` — the on-main response baseline - `/tmp/repro-issue-<ISSUE>-meta.json` — the `{tool, arguments}` used to call it Both must exist. The meta file is how this skill replays the *exact* same call instead of guessing tool and args from the response body. ```bash ls ...