Official agent skill

PR Link Issue

Append a GitHub issue link and its Linear ticket to the current PR's description.

OfficialApache-2.0Auto-check passed

Install PR Link Issue

skills CLI

$ npx skills add getsentry/skills --skill pr-link-issue -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install getsentry/skills pr-link-issue --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/getsentry/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/pr-link-issue .claude/skills/pr-link-issue && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "pr-link-issue" agent skill from https://github.com/getsentry/skills/tree/main/skills/pr-link-issue into .claude/skills/pr-link-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-link-issue", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/getsentry/skills/tree/main/skills/pr-link-issue

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add getsentry/skills --skill pr-link-issue -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install getsentry/skills pr-link-issue --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/getsentry/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/pr-link-issue .agents/skills/pr-link-issue && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "pr-link-issue" agent skill from https://github.com/getsentry/skills/tree/main/skills/pr-link-issue into .agents/skills/pr-link-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-link-issue", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add getsentry/skills --skill pr-link-issue -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install getsentry/skills pr-link-issue --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/getsentry/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/pr-link-issue .cursor/skills/pr-link-issue && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "pr-link-issue" agent skill from https://github.com/getsentry/skills/tree/main/skills/pr-link-issue into .cursor/skills/pr-link-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-link-issue", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/getsentry/skills.git --path skills/pr-link-issue

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add getsentry/skills --skill pr-link-issue -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install getsentry/skills pr-link-issue --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/getsentry/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/pr-link-issue .gemini/skills/pr-link-issue && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "pr-link-issue" agent skill from https://github.com/getsentry/skills/tree/main/skills/pr-link-issue into .gemini/skills/pr-link-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-link-issue", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install getsentry/skills pr-link-issue

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add getsentry/skills --skill pr-link-issue -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/getsentry/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/pr-link-issue .github/skills/pr-link-issue && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "pr-link-issue" agent skill from https://github.com/getsentry/skills/tree/main/skills/pr-link-issue into .github/skills/pr-link-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-link-issue", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add getsentry/skills --skill pr-link-issue -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install getsentry/skills pr-link-issue --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/getsentry/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/pr-link-issue .opencode/skills/pr-link-issue && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "pr-link-issue" agent skill from https://github.com/getsentry/skills/tree/main/skills/pr-link-issue into .opencode/skills/pr-link-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-link-issue", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: pr-link-issue
GitHub stars: 1k
Token cost: ~681 tokens
SKILL.md length: 279 words
Files: 1
Skills in repo: 27
Repo updated: Oct 2, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Append a GitHub issue link and its Linear ticket to the current PR's description.

Works in 7 steps: Resolve the PR number — skip if user… → Extract issue number + repo from the… → Fetch the Linear ticket from the issue's… → …
Asked to link issue to pr
SKILL.md covers Inputs, Steps and Notes
Calls gh; reaches github.com

What it does

PR Link Issue is an agent skill from getsentry/skills, published by the product's own GitHub organization. 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.

Its SKILL.md is about 680 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It works with GitHub and Sentry. The repository describes itself as: Agent Skills used by the Sentry team for development. The licence is Apache-2.0.

When your agent uses it

Asked to link issue to pr
Fill in issue and linear in pr
Add issue refs to pr
Given a GitHub issue URL and asked to attach it to the current PR

Example prompts

“s description. Use when asked to”
“fill in issue and linear in pr”
“add issue refs to pr”
“/pr-link-issue”

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

Resolve the PR number — skip if user supplied one
Extract issue number + repo from the input URL, or accept a bare #1234 for current repo.
Fetch the Linear ticket from the issue's linear-linkback comment
Read the existing PR body so you can append rather than overwrite
Construct the new body. If the body is empty, use just the #### Issues block. Otherwise, append it after a blank line. Don't duplicate…
Update the PR with a heredoc to preserve newlines
Confirm by echoing the resulting PR URL

What it can do on your machine

Read from SKILL.md and the folder at commit d18b7aa. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
- github.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

PR Link Issue loads about 681 tokens when it runs. Until then it costs about 87 tokens; SKILL.md has 279 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~87
When it runs · the whole SKILL.md, loaded when a task matches: ~681

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from getsentry/skills at commit d18b7aa, republished under its Apache-2.0 licence (© getsentry). 279 words, ~681 tokens.

Download SKILL.mdSave it as .claude/skills/pr-link-issue/SKILL.md (or your agent's skills folder).

name: pr-link-issue
description: 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.

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

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.
Extract issue number + repo from the input URL, or accept a bare #1234 for current repo.

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.

Read the existing PR body so you can append rather than overwrite:
bash
```
gh pr view <pr-number> --json body -q '.body'
```
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:
markdown
```
#### Issues

* Resolves: #<n>
* Resolves: <linear-key>
```

Update the PR with a heredoc to preserve newlines:

bash

gh pr edit <pr-number> --body "$(cat <<'EOF'
<new body>
EOF
)"

Confirm by echoing the resulting PR URL:
bash
```
gh pr view <pr-number> --json url -q '.url'
```

Notes

Linear linkback comments are posted by the GitHub user linear-code. The body contains a markdown link whose text is the Linear key, e.g. PY-2357.
Project keys vary per repo (PY-… for sentry-python, JS-… for sentry-javascript, etc.) — the regex [a-z]+-[0-9]+ covers them.
Don't strip existing PR content. Always read first, append/replace second.
If the issue doesn't have a Linear linkback yet (newly filed), proceed with just the GitHub issue reference and tell the user the Linear key is missing.

Files

Just SKILL.md in skills/pr-link-issue of getsentry/skills.

Open the folder on GitHubat commit d18b7aa

Compare with similar skills

PR Link Issue next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

PR Link Issue compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
PR Link Issue this skillgetsentry/skills	1k	—	~681	Automated safety check: Pass	Apache-2.0	4 days ago
Scraps Reviewgetsentry/sentry	45k	—	~1.2k	Automated safety check: Notes	Custom licence	today
Create Pull Request with Work Item IDmakeplane/plane	60k	—	~824	Automated safety check: Pass	AGPL-3.0	yesterday
Dotagentsgetsentry/sentry-wizard	295	—	~900	Automated safety check: Pass	Custom licence	yesterday
Reviewgetsentry/sentry-react-native	1.8k	—	~1.9k	Automated safety check: Pass	MIT	today
Superset Automatesuperset-sh/superset	15k	—	~1.4k	Automated safety check: Pass	Custom licence	today

Similar skills

Scraps Review
getsentry/sentry
Official
Filter large Sentry Scraps design-system migration PRs for review by separating mechanical import-path changes, generated baseline updates, snapshot mocks, and pure renames from substantive…
45k GitHub stars~1.2k tokensUpdated today
Frontend & DesignAuto-check: notes
Create Pull Request with Work Item ID
makeplane/plane
Opens a pull request for the current branch using the repo's template, a work item ID in the title and a description filled in from the actual diff.
60k GitHub stars~824 tokensUpdated yesterday
DevelopmentAuto-check passed
Dotagents
getsentry/sentry-wizard
Official
Manage agent skill dependencies with dotagents. An agent skill from getsentry/sentry-wizard.
295 GitHub stars~900 tokensUpdated yesterday
Agent WorkflowsAuto-check passed
Review
getsentry/sentry-react-native
Official
Three-axis review of the branch diff — Standards (this repo's documented standards + public API/bridge surface), Spec (the originating Linear/GitHub issue or PR), and Correctness (runtime bugs + the…
1.8k GitHub stars~1.9k tokensUpdated today
Agent WorkflowsAuto-check passed
Superset Automate
superset-sh/superset
Turns a recurring chore into a scheduled or event-triggered Superset agent, drafting its prompt, picking a target and trigger, and reviewing the first run.
15k GitHub stars~1.4k tokensUpdated today
Productivity & AutomationAuto-check passed
Spec
getsentry/sentry-react-native
Official
Produce a verified spec — problem, desired outcome, and acceptance criteria — before building.
1.8k GitHub stars~1.1k tokensUpdated today
Product & Project ManagementAuto-check passed

Questions about PR Link Issue

What does PR Link Issue do?

Append a GitHub issue link and its Linear ticket to the current PR's description. PR Link Issue is an agent skill from getsentry/skills, published by the product's own GitHub organization. Append a GitHub issue link and its Linear ticket to the current PR's description.

When should I use PR Link Issue?

PR Link Issue fits situations like: asked to link issue to pr; fill in issue and linear in pr; add issue refs to pr; given a GitHub issue URL and asked to attach it to the current PR.

How do I install PR Link Issue in Claude Code?

Run `npx skills add getsentry/skills --skill pr-link-issue -a claude-code`. Or copy the skill folder (skills/pr-link-issue in getsentry/skills) into .claude/skills/pr-link-issue in your project. Claude Code loads it when a task matches its description.

How do I install PR Link Issue in Codex?

Run `npx skills add getsentry/skills --skill pr-link-issue -a codex`. Or copy the skill folder (skills/pr-link-issue in getsentry/skills) into .agents/skills/pr-link-issue in your project. Codex loads it when a task matches its description.

Can I use PR Link Issue in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add getsentry/skills --skill pr-link-issue -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pr-link-issue, .gemini/skills/pr-link-issue, .github/skills/pr-link-issue and .opencode/skills/pr-link-issue in your project.

What does PR Link Issue need to run?

Going by SKILL.md and its folder, PR Link Issue needs the command-line tools its instructions call (gh).

Does PR Link Issue access the network?

SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is PR Link Issue safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does PR Link Issue use?

PR Link Issue is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does PR Link Issue use?

About 681 tokens (SKILL.md is roughly 2.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to PR Link Issue?

Skills that share tags, products or a category with PR Link Issue: Scraps Review (getsentry/sentry, 45k stars), Create Pull Request with Work Item ID (makeplane/plane, 60k stars), Dotagents (getsentry/sentry-wizard, 295 stars) and Review (getsentry/sentry-react-native, 1.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains PR Link Issue?

getsentry (a GitHub organization, an official publisher) maintains it in getsentry/skills, which has 1,037 GitHub stars. The repository holds 27 skills in this directory. The repository was last updated on October 2, 2026.

Source: getsentry/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

PR Link Issue

Install PR Link Issue

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Link a GitHub Issue + Linear Ticket on a PR

Inputs

Steps

Notes

Files

Compare with similar skills

Similar skills

Scraps Review

Create Pull Request with Work Item ID

Dotagents

Review

Superset Automate

Spec

More from getsentry/skills

Skill Scanner

Gh Review Requests

Security Review

Skill Writer

Django Access Review

Gha Security Review

Questions about PR Link Issue

Install PR Link Issue

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Link a GitHub Issue + Linear Ticket on a PR

Inputs

Steps

Notes

Files

Compare with similar skills

Similar skills

More from getsentry/skills

Related

Questions about PR Link Issue