skills.rest
tr4m0ryp
tr4m0rypCOMMUNITY
Explore all skills by this author →
𝕏@tr4m0rypGitHub

3-verify-pr-fix

Compare tool call outputs before and after a pull request fix.

Updated Jul 10, 2026
Search Tags:#code review#issue tracking#LinkedIn#PR verification#diff comparison
One-click install
npx skills add https://github.com/tr4m0ryp/linkedin-mcp-server --skill 3-verify-pr-fix-tr4m0ryp
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: 3-verify-pr-fix
Source: https://github.com/tr4m0ryp/linkedin-mcp-server/tree/main/.agents/skills/3-verify-pr-fix
Command: npx skills add https://github.com/tr4m0ryp/linkedin-mcp-server --skill 3-verify-pr-fix-tr4m0ryp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill is designed to verify if a pull request fixes a specific issue on the LinkedIn MCP server by comparing the outputs of the tool call before and after the fix.

Core Features & Use Cases

  • PR Verification: Checks out a candidate PR locally, restarts the MCP server on the PR branch, and compares the outputs of the same tool call that failed in the main branch.
  • Auditing: Audits the fix for locale-independence, DOM-stability, and scope according to specific scraping rules.
  • Use Case: When a user asks whether a candidate PR actually solves a previously-reproduced issue, this skill can be used to verify the fix.

Quick Start

To verify a PR, use the command: verify-pr <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 if a pull request actually fixes a LinkedIn MCP server issue?▼

PR verification checks out the candidate PR locally, restarts the MCP server on the PR branch, and compares the tool call outputs before and after the fix to confirm the issue is resolved.

What do I need to capture before verifying a PR fix?▼

PR verification requires a previously captured baseline of the failed tool call output from the main branch, a local checkout of the candidate PR, and an MCP server restart to execute the comparison.

How do I start verifying a PR fix using the command line?▼

To verify a PR fix, use the command `verify-pr <pr-number>` to automatically check out the PR locally, restart the MCP server, and compare the before and after tool call outputs.

Does PR verification audit the code quality of the fix itself?▼

Yes, PR verification audits the fix for locale-independence, DOM-stability, and scope according to specific scraping rules, ensuring the code meets required standards beyond just resolving the issue.

Can I use this PR verification for issues without a captured baseline?▼

No, PR verification assumes a baseline has already been captured for the issue. Without the prior tool call output from the main branch, there is no reference to compare against after the fix.

Why is restarting the MCP server necessary for PR verification?▼

Restarting the MCP server is required to apply the PR branch changes locally, allowing the verification process to execute the same tool call that previously failed and compare the new output against the baseline.

Related Skills

Explore More Software Engineering Skills→
ncukondoncukondo
5

review-pr-local

Review GitHub PRs from the main repository using gh CLI commands.

Community
Intermediate
earayuearayu
34

dev-lifecycle

Automate Git lifecycle workflows from feature branches to production deployment.

Community
Advanced
stickerdanielstickerdaniel
3.1k

3-verify-pr-fix

Replay MCP tool calls on PR branches and diff results against baselines.

Community
Advanced
steadyfallsteadyfall

benchmark

Collect end-to-end web performance metrics from the browse daemon across pages.

Community
Advanced