Skills

Skill 17 of 27

PR Link Issue

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

1 minute · 272 words · 4 sections

Install

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

$ npx skills add getsentry/skills

» /plugin marketplace add getsentry/skills

The first command installs just this skill, by the name in its SKILL.md; the second installs the whole repository.

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:
```
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:

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:
```
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:
```
#### Issues

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

Update the PR with a heredoc to preserve newlines:

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

Confirm by echoing the resulting PR URL:

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.

About this skill

Trigger

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.

The verbatim description from this skill’s front matter — the string an agent matches on to decide whether to load it.

Colophon for this issue

Colophon

How this issue was made

Source

github.com/getsentry/skills, branch main, last pushed 21 September 2026.

Licence

Apache-2.0 — the text of every skill is reproduced unmodified, frontmatter included, under the upstream licence.

Discovery

27 skills found by walking the repository tree for SKILL.md, not by matching a directory convention. One layout observed: skills/*/SKILL.md.

Issue colours

Resolved from a deterministic hash of the owner name. Two accent tones are generated per issue and each is proven against its own ground before it ships: a single accent that passes AA on both light and dark paper is arithmetically impossible.

Heading repairs

1 repair applied to this skill so the document has one h1 and no skipped levels:

Shifted “4 headings” from h1 to h2 so the skill title is the only h1.

Spec compliance

Every skill satisfies the Agent Skills specification’s frontmatter rules.

Images

Images inside a skill come from the upstream repository. Where the author gave no alternative text we mark the image decorative rather than inventing a description — a plausible caption we made up is worse than none for the reader who depends on it.

Marketplace

A plugin manifest is published at .claude-plugin/marketplace.json by Sentry, declaring 1 plugin. It is read for editorial metadata only — never as the skill index, which is always the repository tree.

Signal

Install counts come from skills.sh. They measure downloads, not quality, and an unranked repository is not an unread one.

Agent surfaces

The whole issue is available as one markdown document at /getsentry/skills.md, and each skill at its own .md URL.

Publication

Set by Skills Docs from the source repository. Body text is Literata at the reader’s chosen size and measure; code is Geist Mono. Nothing on this page was written by us except this paragraph.

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.

<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.

Resolve the PR number — skip if user supplied one:

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:

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:

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:

#### Issues

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

Update the PR with a heredoc to preserve newlines:

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

Confirm by echoing the resulting PR URL:

gh pr view <pr-number> --json url -q '.url'

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.