# 3 Verify PR Fix

Verify PR #N, does this PR fix #M, check the fix in #N, or test the candidate PR.

- Repository: https://github.com/stickerdaniel/linkedin-mcp-server (4081 stars)
- Category: Testing
- License: Apache-2.0
- Last updated: 2026-10-31
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add stickerdaniel/linkedin-mcp-server --skill 3-verify-pr-fix -g -a claude-code -y`
Codex: `npx skills add stickerdaniel/linkedin-mcp-server --skill 3-verify-pr-fix -g -a codex -y`
Cursor: `npx skills add stickerdaniel/linkedin-mcp-server --skill 3-verify-pr-fix -g -a cursor -y`
Gemini CLI: `npx skills add stickerdaniel/linkedin-mcp-server --skill 3-verify-pr-fix -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add stickerdaniel/linkedin-mcp-server`

## Description

Verify PR #N, does this PR fix #M, check the fix in #N, or test the candidate PR.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Verify a candidate PR

Review the packet, the candidate diff, and relevant tests. Live comparison against a captured baseline is optional. No edits, no merges, no pushes.

## 1. Resolve the PR and its linked issue

```bash
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 which one is the verification target.

Read that issue's packet and comments.

## 2. Packet, diff, and tests

This path does not need `/tmp/repro-issue-$ISSUE-main.json`. Absence of a local baseline limits the live branch, not the whole PR verdict. Do not create fake success or failure files.

```bash
gh pr diff $PR --repo $REPO
gh pr view $PR --repo $REPO --json files --jq '.files[].path'
```

Hard flags (any one downgrades a clean live pass to concerns):

- Locale-dependent detection: `== "Connect"`, `in ["Pending", "Follow"]`, `contains("1st")`, `aria-label="..."` with translated text. Attribute presence is the locale-independent signal.
- LinkedIn class-name selectors: `.entity-result__item`, `.artdeco-button__text`. Minimal generic selectors only (`a[href*="/jobs/view/"]`).
- Multiple navigations behind one `PERSON_SECTIONS` / `COMPANY_SECTIONS` entry.
- Missing tests beside the canonical owner from `docs/linkedin-architecture.md`.

A supplied capture or regression fixture can support a before-and-after claim within its scope. Protocol or startup failures are execution limits, not a pass.

The rest: https://github.com/stickerdaniel/linkedin-mcp-server/blob/HEAD/.agents/skills/3-verify-pr-fix/SKILL.md