getsentry/pr-link-issue
skills/pr-link-issue/SKILL.md
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 --global
skillsauthnpx skillsauth add getsentry/skills pr-link-issueInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 22, 2026, 3:52 AM118.9s1 file scanned
SKILL.md
- 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 likehttps://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
#1234for 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 -1If 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
#### Issuesblock. Otherwise, append it after a blank line. Don't duplicate — if#### Issuesis 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.
Related Skills
getsentry/claude-settings-audit
tools
VerifiedTrustedOfficial
Analyze a repository to generate recommended Claude Code settings.json permissions. Use when setting up a new project, auditing existing settings, or determining which read-only bash commands to allow. Detects tech stack, build tools, and monorepo structure.
770SKILL.mdUpdated Apr 20, 2026
getsentry/triage-frontend-issues
development
VerifiedTrustedOfficial
Triage new issues in the Sentry `javascript` project by archiving non-actionable noise. Use when asked to "triage issues", "triage the javascript project", "archive non-actionable issues", "triage new frontend issues", or "clean up the sentry/javascript queue". Operates only on the sentry/javascript project, only archives (never resolves), and always archives with `untilEscalating`.
733SKILL.mdUpdated May 22, 2026
getsentry/iterate-pr
testing
VerifiedTrustedOfficial
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.
725SKILL.mdUpdated Apr 20, 2026
getsentry/pr-writer
documentation
VerifiedTrustedOfficial
Create and update pull requests following Sentry conventions. Use when opening a PR or refreshing an existing PR after material changes.
722SKILL.mdUpdated Apr 20, 2026