3-verify-pr-fix

Verify a candidate PR fixes a reproduced issue by replaying the same MCP tool call and diffing outputs.

Updated Aug 6, 2026
One-click install
npx skills add https://github.com/kaistenberg/MCP-Linkedin --skill 3-verify-pr-fix-kaistenberg
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: 3-verify-pr-fix
Source: https://github.com/kaistenberg/MCP-Linkedin/tree/main/.agents/skills/3-verify-pr-fix
Command: npx skills add https://github.com/kaistenberg/MCP-Linkedin --skill 3-verify-pr-fix-kaistenberg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When reviewing a pull request that claims to fix a bug in the LinkedIn MCP server, maintainers need proof the fix actually works against the real LinkedIn site, not just a code read. This Skill checks out the PR locally, restarts the MCP server on the PR branch, replays the exact tool call that failed on main, diffs the outputs, and audits the diff against the project's scraping rules. ## Core Features & Use Cases - Baseline Replay: Reads the on-main baseline and tool-call metadata written by /2-repro-issue from /tmp, then replays the identical MCP tools/call over streamable HTTP against the PR branch. - Verdict Classification: Classifies the PR as fixes, fixes with concerns, does not fix, cannot run, or cannot verify (skill limitation), with evidence lines from the output diff. - Scraping Rule Audit: Flags locale-dependent string matching, LinkedIn CSS-class selectors, multi-navigation section mappings, and missing tests per CLAUDE.md rules. - Use Case: A maintainer asks "does PR #498 fix issue #470?" — the Skill fetches the PR, runs the same get_person_profile call that failed on main, diffs the JSON responses, and reports a verdict with merge recommendation. ## Quick Start Verify whether PR #498 fixes the issue reproduced earlier by running this Skill with the PR number.

Frequently Asked Questions about 3-verify-pr-fix

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify a PR fixes a GitHub issue locally?▼

Check out the PR head as a detached HEAD, restart the MCP server on a free port, replay the exact tool call that failed on main, and diff the JSON responses. This Skill automates that flow using gh, git, curl, and jq.

How to test an MCP server fix with the same tool call?▼

Store the tool name and arguments in a meta JSON file during reproduction, then replay them verbatim via a tools/call JSON-RPC request over streamable HTTP after checking out the fix branch. Restarting the server is required because running workers hold stale code.

Does this Skill work without running /2-repro-issue first?▼

No. It requires the on-main baseline and meta files at /tmp/repro-issue-<issue>-main.json and -meta.json written by /2-repro-issue. If either is missing or empty, it stops and asks you to run the reproduction skill first.

What scraping rules does the PR audit check?▼

The audit flags locale-dependent string matching like == "Connect", LinkedIn CSS-class selectors such as .artdeco-button__text, section mappings that require multiple navigations, and bug fixes missing tests in tests/test_scraping.py. Any flag downgrades the verdict to fixes-with-concerns.

What happens if the bug cannot be reproduced as a failure baseline?▼

The Skill reports "Cannot verify fix (skill limitation)" instead of criticizing the PR. It falls back to a regression check that the baseline call still succeeds on the PR branch plus a code audit of the diff.

Does verifying a PR modify the branch or push changes?▼

No. The Skill uses a detached HEAD checkout of FETCH_HEAD, installs an EXIT trap to return to the original ref, and never edits, merges, or pushes. It only verifies and reports a verdict.