speckit-github-issues-link

Link spec.md files to GitHub issues with reverse reference comments.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/B0yZ4kr14/OrthoPlus-Enterprise --skill speckit-github-issues-link
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-github-issues-link
Source: https://github.com/B0yZ4kr14/OrthoPlus-Enterprise/tree/main/.specify-backups/20260518-141826/_agents/skills/speckit-github-issues-link
Command: npx skills add https://github.com/B0yZ4kr14/OrthoPlus-Enterprise --skill speckit-github-issues-link

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of missing traceability between a specification artifact and the original GitHub issue that drove the change, making review and synchronization harder.

Core Features & Use Cases

  • Bidirectional traceability: Adds issue link details into the spec and creates a comment on the GitHub issue pointing back to the spec.
  • Flexible issue targeting: Accepts input as owner/repo#issue_number or just #issue_number to use the current repository.
  • Spec discovery from feature context: Locates the correct feature directory and spec.md to update based on the current branch naming pattern.

Example use case: You create a new spec for a feature, then want the relevant GitHub issue linked to the spec so future updates stay connected.

Quick Start

Provide the issue reference as #2175 or owner/repo#2175 while running this skill in the feature directory that contains the spec.md to automatically add links in both places.

Frequently Asked Questions about speckit-github-issues-link

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

FAQPage Schema
How do I link a spec.md file to a GitHub issue?

To link a spec.md file to a GitHub issue, you provide an issue reference like #2175 while running the skill in your feature directory, which updates the spec with the link and posts a reverse reference comment to the issue.

What is bidirectional traceability between spec artifacts and GitHub issues?

Bidirectional traceability means adding the GitHub issue link directly into the spec.md file while simultaneously posting a comment on the GitHub issue that points back to the specification artifact.

Do I need GitHub CLI to connect spec-kit artifacts with GitHub issues?

Yes, you need the GitHub CLI (gh) installed and authenticated to use this skill, as it relies on the CLI to parse issue references and post comments back to the GitHub repository.

How do I add a reverse reference comment to a GitHub issue from a feature branch?

You add a reverse reference comment by running the skill with an issue input like owner/repo#issue_number, which automatically locates your spec.md from the branch context and posts the comment.

Can I use issue numbers without specifying the repository owner and name?

Yes, you can input just the issue number using the #issue_number format, and the skill will automatically target the current repository configured in your environment.

How does spec discovery work when linking documentation to GitHub issues?

Spec discovery works by matching the current branch naming pattern to locate the correct feature directory and identify the target spec.md file for updating with the GitHub issue link.