skills.rest
LumaKernel
LumaKernelCOMMUNITY
Explore all skills by this author →
𝕏@lumc_GitHub

linking-github

Adds hyperlinks to technical terms and file paths in GitHub issue and PR bodies.

17|1|Updated Dec 29, 2019
Search Tags:#documentation#markdown#pull request#github#gh cli#issue#linking
One-click install
npx skills add https://github.com/LumaKernel/dotfiles --skill linking-github-lumakernel
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: linking-github
Source: https://github.com/LumaKernel/dotfiles/tree/main/common/claude/skills/linking-github
Command: npx skills add https://github.com/LumaKernel/dotfiles --skill linking-github-lumakernel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? GitHub issue and PR descriptions often mention file paths, function names, technical terms, and other issues as plain text, forcing readers to manually search for each reference. This Skill detects those references and converts them into clickable links without altering the original wording. ## Core Features & Use Cases - File Path and Code Linking: Converts file paths, class names, and function names into GitHub permalinks with line numbers after verifying they actually exist in the repository. - Technical Term Linking: Links library names, RFCs, and cloud service names to their official documentation or repositories. - GitHub Cross-Reference Conversion: Transforms plain-text mentions like "issue 123" into #123 format and commit SHAs into commit links. - Use Case: After writing a detailed bug report referencing src/auth/login.ts:42 and a related discussion in another issue, run this Skill to turn every reference into a verified link while keeping your text untouched. ## Quick Start Link the technical terms and file paths in PR number 15 of this repository without changing the body text.

Frequently Asked Questions about linking-github

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add links to file paths in a GitHub PR description?▼

Fetch the PR body with gh api, identify file paths and code references, verify each path exists in the repository, then patch the body with Markdown links to GitHub permalinks. Line-numbered references like foo.ts:42 become line-anchored links.

How to update a GitHub issue body using the gh CLI?▼

Use gh api repos/{owner}/{repo}/issues/{number} -X PATCH -F body=@file to update an issue body. Write the updated content to a temporary file first and pass it with the @ syntax to avoid shell escaping problems.

Why does gh pr view fail and what is the alternative?▼

gh pr view can fail due to the deprecation of Projects Classic. Use gh api repos/{owner}/{repo}/pulls/{number} --jq '.body' instead to reliably retrieve PR bodies through the REST API.

Does linking GitHub issue bodies change the original text?▼

No, the original wording and expressions remain completely unchanged. Only Markdown link syntax is added around existing references, already-linked sections are left untouched, and uncertain targets are never linked by guesswork.

Can I link plain-text issue mentions like issue 123 to real references?▼

Yes, plain-text mentions such as "issue 123" are converted to #123 auto-link format, and references to other repositories become owner/repo#123. Commit SHAs are converted into GitHub commit links.

Related Skills

Explore More Software Engineering Skills→
zebbernzebbern
5

pr-writer

Draft GitHub pull request descriptions following Sentry conventions.

Community
Advanced
CodingThrustCodingThrust
35

review-pipeline

Automates GitHub Pull Request triage and progression through board statuses.

Official
Advanced
getty104getty104
4

read-github-issue

Extract and structure GitHub Issue data with labels, assignees, and milestones.

Community
Advanced
juspayjuspay
47

hk

Mutate GitHub issues into linked knowledge graph nodes via gh api.

Official
Advanced