speckit-github-issues-sync

Sync spec.md files with linked GitHub Issue title, labels, state, and comments.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of spec documents going stale when the linked GitHub Issue is edited, so the spec no longer matches the latest title, labels, status, or discussion notes.

Core Features & Use Cases

  • Detects issue changes since last sync by comparing GitHub issue updatedAt with last_synced stored in .issue-link metadata.
  • Syncs spec fields from the GitHub Issue by updating the spec markdown with the latest Issue Status, Labels, Last Updated, and feature title.
  • Appends newly created issue comments into a “New Comments” section after the previous sync timestamp.
  • Use case: You imported specs from GitHub Issues, and during ongoing review the issue gets new comments and label/status changes; you run this Skill to update the corresponding feature specs automatically.

Quick Start

Run /speckit.github-issues-sync with no arguments to sync all linked issues, or provide a specific feature directory name or issue number to sync only that target.

Frequently Asked Questions about speckit-github-issues-sync

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

FAQPage Schema
How do I sync spec markdown files with GitHub issue updates?

You can sync spec markdown files with GitHub issue updates by running a command that compares the issue's updatedAt timestamp with the last_synced metadata in your .issue-link file, then automatically propagates new titles, labels, states, and comments into the spec.

What is the best way to keep Spec-Kit project artifacts updated with new GitHub issue comments?

Keeping Spec-Kit artifacts updated involves a synchronization process that appends newly created GitHub issue comments into a dedicated section of your spec.md file, automatically inserting them after the previous sync timestamp.

Do I need GitHub CLI authentication to sync issues with spec files?

Yes, you need GitHub CLI authentication to sync issues with spec files, alongside an existing .specify project structure where your spec.md files are linked to issues via .issue-link metadata for the process to function.

Can I sync a specific GitHub issue instead of all linked specs?

Yes, you can sync a specific GitHub issue by providing a targeted feature directory name or issue number as an argument; running the command with no arguments defaults to syncing all linked issues.

Why are my spec documents going stale after editing the linked GitHub issue?

Spec documents go stale because manual edits to a GitHub issue are not automatically reflected in the spec.md file, requiring a synchronization step to update the title, labels, status, and discussion notes.

What metadata is required to link a spec file to a GitHub issue?

Linking a spec file to a GitHub issue requires .issue-link metadata containing the last_synced timestamp, operating within a .specify project structure to properly track when changes were last propagated.