← ClaudeAtlas

uselink-pr-digestlisted

Summarize a pull request as a stakeholder-friendly HTML page and publish to uselink. Use when the user wants to share PR changes with PMs, reviewers, or business stakeholders who don't read diffs.
spartan-hieuvo/claude-skills · ★ 0 · Web & Frontend · score 73
Install: claude install-skill spartan-hieuvo/claude-skills
# PR Digest → Uselink Turn a pull request into a clean, readable summary page and publish it to uselink. Stakeholders see what changed and why — without reading diffs. ## When to Use - "Summarize this PR for the PM" - "Share PR #42 with the team" - "Create a digest of what this branch does" - User provides a PR number or URL ## Prerequisites ```bash which uselink || echo "MISSING" test -f ~/.uselink/config.json && echo "OK" || echo "NO_CONFIG" which gh || echo "GH_MISSING" ``` If `uselink` or its config is missing, tell the user to install/configure it. `gh` CLI is needed for PR metadata. ## Workflow ### 1. Get PR data **From PR number:** ```bash gh pr view <number> --json title,body,author,state,additions,deletions,changedFiles,baseRefName,headRefName,mergedAt,createdAt,labels,reviewDecision gh pr diff <number> --stat gh pr diff <number> --name-only ``` **From current branch (no PR number given):** ```bash gh pr view --json title,body,author,state,additions,deletions,changedFiles,baseRefName,headRefName,mergedAt,createdAt,labels,reviewDecision git diff origin/main...HEAD --stat git diff origin/main...HEAD --name-only ``` **From URL:** Extract `owner/repo` and `number` from the URL pattern `github.com/<owner>/<repo>/pull/<number>`. ### 2. Analyze changes ```bash # Get the full diff for analysis gh pr diff <number> # Or for current branch git diff origin/main...HEAD ``` Read each changed file and categorize changes: - **New features** — new files, new endpoints,