PR Link Issue
Append a GitHub issue link and its Linear ticket to the current PR's description. Use when asked to "link issue to pr", "fill in issue and linear in pr", "add issue refs to pr", or when given a GitHub issue URL and asked to attach it to the current PR. Resolves the Linear ticket automatically from the issue's linear-linkback comment.
Install
/plugin marketplace add getsentry/skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add getsentry/skills --skill pr-link-issuegit clone --depth 1 https://github.com/getsentry/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/skills/pr-link-issue ~/.claude/skills/pr-link-issuePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Link a GitHub Issue + Linear Ticket on a PR
Appends a Sentry-style `#### Issues` block to a PR description, referencing both the GitHub issue and the Linear ticket pulled from the issue's `linear-linkback` comment.
## Inputs
- `<issue-url>` — GitHub issue URL like `https://github.com/<owner>/<repo>/issues/<n>`. Issue number alone is fine if the PR is in the same repo.
- (optional) `<pr-number>` — defaults to the open PR for the current branch.
## Steps
1. **Resolve the PR number** — skip if user supplied one:
```bash
gh pr view --json number,body -q '.number'
```
If no PR exists on the branch, stop and tell the user.
2. Extract issue number + repo from the input URL, or accept a bare `#1234` for current repo.
3. Fetch the Linear ticket from the issue's linear-linkback comment:
```bash
gh issue view <n> --repo <owner>/<repo> --json comments \
-q '.comments[] | select(.author.login=="linear-code") | .body' \
| grep -Eioe '[a-z]+-[0-9]+' | head -1
```
If no match, fall back to asking the user for the Linear key, or omit it.
4. Read the existing PR body so you can append rather than overwrite:
```bash
gh pr view <pr-number> --json body -q '.body'
```
5. Construct the new body. If the body is empty, use just the `#### Issues` block. Otherwise, append it after a blank line. Don't duplicate — if `#### Issues` is already present, replace that section instead of adding a second one.
Format:Details
- Skill name
pr-link-issue- Repository
- getsentry/skills
- Path
skills/pr-link-issue/SKILL.md- License
- Apache-2.0
- Repo updated
- 14 November 2026
- Listed in
- heilcheng/awesome-agent-skills
FAQ
What does the PR Link Issue skill do?
Append a GitHub issue link and its Linear ticket to the current PR's description. Use when asked to "link issue to pr", "fill in issue and linear in pr", "add issue refs to pr", or when given a GitHub issue URL and asked to attach it to the current PR. Resolves the Linear ticket automatically from the issue's linear-linkback comment.
How do I install the PR Link Issue skill?
Claude Code plugin: /plugin marketplace add getsentry/skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is PR Link Issue popular?
It lives in getsentry/skills, which has 1,179 GitHub stars and 70 forks, and is included in 1 curated skill list.
Related skills
Doc Coauthoring
1.2kgetsentry/skills
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Brand Guidelines
1.2kgetsentry/skills
Write copy following Sentry brand guidelines. Use when writing UI text, error messages, empty states, onboarding flows, 404 pages, documentation, marketing copy, or any user-facing content. Covers both Plain Speech (default) and Sentry Voice tones.
Code Simplifier
1.2kgetsentry/skills
Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Use when asked to "simplify code", "clean up code", "refactor for clarity", "improve readability", or review recently modified code for elegance. Focuses on project-specific best practices.
PR Screenshots
1.2kgetsentry/skills
Capture screenshots of the Sentry UI in a web browser, lay them out in a pull request description as before/after tables, and upload them with `gh --attach`.
Iterate PR
1.2kgetsentry/skills
Iterate on a PR until actionable CI passes and high/medium review feedback is addressed. Use for PR CI failures, review feedback, or green-check loops; do not wait for human approval, draft status, or merge gates.
PR Writer
1.2kgetsentry/skills
Create or refresh reviewer-facing PR titles and descriptions. Use when opening a PR, updating its title or body, or preparing branch changes for review.
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.