skills.rest
alunduil
alunduilCOMMUNITY
Explore all skills by this author →
Website𝕏@alunduilGitHub

issue-links

Relate GitHub issues and PRs with Closes, blocked-by, or parent/sub-issue edge types.

1|2|Updated Apr 23, 2026
Search Tags:#github#pr#blocks#issue-linking#edge-type#closes#parent-sub-issue
One-click install
npx skills add https://github.com/alunduil/alunduil-chezmoi --skill issue-links
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: issue-links
Source: https://github.com/alunduil/alunduil-chezmoi/tree/main/dot_claude/skills/issue-links
Command: npx skills add https://github.com/alunduil/alunduil-chezmoi --skill issue-links

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Relating GitHub issues and PRs with the correct edge types to improve traceability, dependency awareness, and workflow clarity.

Core Features & Use Cases

  • Edge selection: determine the strongest accurate relation among Closes, blocked-by, parent/sub-issue, or plain mentions.
  • Impact propagation: routes dependencies and progress updates through the issue graph for better project visibility.
  • Use Case: when a PR fixes an issue, this skill ensures Closes is used; when work must wait on another task, blocked-by is applied; when decomposition occurs, parent/sub-issues are linked.

Quick Start

Link an issue and a PR by applying the strongest accurate edge (Closes/Resolves, blocked-by, parent/sub-issue, or plain mention) according to GitHub conventions.

Frequently Asked Questions about issue-links

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

FAQPage Schema
How do I link GitHub PRs to issues with the correct edge type?▼

To link GitHub PRs to issues, apply the strongest accurate edge such as Closes, blocked-by, or parent/sub-issue based on dependency semantics and repository workflow conventions.

When should I use blocked-by versus parent/sub-issue edges in GitHub?▼

Use blocked-by when work must wait on another task, and parent/sub-issue when decomposing a larger task into smaller linked issues for better dependency tracking.

What is the best way to propagate dependency impact across a GitHub issue graph?▼

Propagating dependency impact requires selecting precise edge types like Closes or blocked-by to route progress updates through the issue graph for improved project visibility.

Does plain mention linking work for tracking PR progress on GitHub issues?▼

Plain mentions link issues and PRs but do not propagate dependencies or progress updates like stronger edge types such as Closes or parent/sub-issue relationships.

Can I automate edge selection for GitHub issue linking based on repository conventions?▼

Edge selection can be determined by evaluating PR and issue bodies against repository workflow conventions to choose the most accurate Closes, blocked-by, or parent/sub-issue relationship.

Related Skills

Explore More Software Engineering Skills→
kinneyyankinneyyan
2

code-review

Analyze git changes to identify critical and high-priority issues.

Community
Advanced
richkuorichkuo
45

milestoneplan

Aggregate GitHub milestone issue data into a structured markdown table.

Community
Intermediate
shellicarshellicar

github-repos

Configure GitHub repository settings and enforce branch protection rules via the gh CLI.

Community
Intermediate
SvendsysSvendsys

to-issues

Create GitHub issues from aligned features using predefined templates.

Community
Intermediate