SkillsAdd

getsentry/skills · Official

pr-link-issue

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

Trending #7662 First seen May 21, 2026

Installation

$ npx skills add getsentry/skills --skill pr-link-issue
View on skills.sh ↗ GitHub repository ↗

Summary

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

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

flutter-fix-layout-issues Similar name
flutter/agent-plugins

Fixes Flutter layout errors (overflows, unbounded constraints) using Dart and Flutter MCP tools…

31.9K installs
github-issues Similar name
github/awesome-copilot

Create, update, and manage GitHub issues using MCP tools. Use this skill when users want to cre…

15.5K installs
my-issues Similar name
github/awesome-copilot 9.6K installs
create-github-issues-feature-from-implementation-plan Similar name
github/awesome-copilot

Create GitHub Issues from implementation plan phases using feature_request.yml or chore_request…

9.3K installs
create-github-issues-for-unmet-specification-requirements Similar name
github/awesome-copilot

Create GitHub Issues for unimplemented requirements from specification files using feature_requ…

9K installs
create-github-issue-feature-from-specification Similar name
github/awesome-copilot

Create GitHub Issue for feature request from specification file using feature_request.yml templ…

8.9K installs

Also in this package

Other skills from getsentry/skills · top by installs.

npx skills add getsentry/skills
security-review 15.5K code-simplifier 7.8K find-bugs 5.4K agents-md 5.2K code-review 4.7K commit 4.2K gha-security-review 4K iterate-pr 4K pr-writer 3.9K claude-settings-audit 3.9K

Browse all from getsentry/skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 986
License LICENSE
Default branch main
Open issues 5
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,735 B
  • docs SUMMARY.md 356 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 736 installs

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.

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

  1. Read the existing PR body so you can append rather than overwrite:

``bash gh pr view <pr-number> --json body -q '.body' ``

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

  1. Update the PR with a heredoc to preserve newlines:

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

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