feat: add GitHub Issues Integration to community catalog

[Fatima367]

Summary

Adds the GitHub Issues Integration extension to the community catalog, enabling users to
generate spec artifacts directly from GitHub Issues.

Resolves #2175

Extension Details

• Name: GitHub Issues Integration
• ID: github-issues
• Version: 1.0.0
• Category: integration
• Effect: Read+Write
• Author: @Fatima367
• Repository: https://github.com/Fatima367/spec-kit-github-issues
• License: MIT

Features

• /speckit.github-issues.import - Import GitHub Issue and generate structured spec.md
• /speckit.github-issues.sync - Keep specs updated when source issues change
• /speckit.github-issues.link - Add bidirectional traceability between specs and issues

Problem Solved

Developers already document requirements in GitHub Issues but then rewrite everything from
scratch in spec.md when starting SDD. This extension eliminates that duplicate work by:

• Importing issues directly into structured specs
• Preserving valuable discussions and context
• Maintaining sync between issues and specs
• Providing bidirectional traceability

Installation

specify extension add github-issues --from
https://github.com/Fatima367/spec-kit-github-issues/archive/refs/tags/v1.0.0.zip

##  Prerequisites

- GitHub CLI (gh) installed and authenticated
- Read access to target repositories
- Write access for bidirectional linking (optional)

##  Testing

✅ Extension tested locally with issue #2175
✅ Successfully imported issue and generated spec.md
✅ Extension manifest validates correctly
✅ GitHub release v1.0.0 created

## Changes Made

extensions/catalog.community.json

- Added github-issues entry in alphabetical order (between fleet and iterate)
- Updated updated_at timestamp to 2026-04-12T12:06:00Z
- Included all required fields: name, id, description, author, version, download_url,
repository, homepage, documentation, changelog, license, requires, provides, tags

##  README.md

- Added GitHub Issues Integration to Community Extensions table
- Positioned alphabetically between Fleet Orchestrator and Iterate
- Included description, category, effect, and repository link

##  Catalog Entry

"github-issues": {
  "name": "GitHub Issues Integration",
  "id": "github-issues",
  "description": "Generate spec artifacts from GitHub Issues - import issues, sync updates, and   maintain bidirectional traceability",
  "author": "Fatima367",
  "version": "1.0.0",
  "download_url":
"https://github.com/Fatima367/spec-kit-github-issues/archive/refs/tags/v1.0.0.zip",
  "repository": "https://github.com/Fatima367/spec-kit-github-issues",
  "homepage": "https://github.com/Fatima367/spec-kit-github-issues",
  "documentation": "https://github.com/Fatima367/spec-kit-github-issues/blob/main/README.md",  
  "changelog": "https://github.com/Fatima367/spec-kit-github-issues/blob/main/CHANGELOG.md",   
  "license": "MIT",
  "requires": {
    "speckit_version": ">=0.1.0",
    "tools": [
      {
        "name": "gh",
        "version": ">=2.0.0",
        "required": true
      }
    ]
  },
  "provides": {
    "commands": 3,
    "hooks": 0
  },
  "tags": [
    "integration",
    "github",
    "issues",
    "import",
    "sync",
    "traceability"
  ],
  "verified": false,
  "downloads": 0,
  "stars": 0,
  "created_at": "2026-04-12T00:00:00Z",
  "updated_at": "2026-04-12T00:00:00Z"
}

##  Checklist

- Extension entry added to extensions/catalog.community.json in alphabetical order
- Extension added to Community Extensions table in README.md
- Catalog updated_at timestamp updated
- All required fields included in catalog entry
- GitHub repository exists with extension code
- GitHub release v1.0.0 created
- Extension tested and working
- Documentation complete (README, CHANGELOG, LICENSE)
- Extension follows naming conventions (speckit.{ext-id}.{command})

###  Related PRs

- First PR: ##2187 - Added extension code to main repository (bundled approach)
- This PR: Adds extension to community catalog for standalone installation

### Notes

The extension is now available as a standalone package that users can install from the
community catalog. The extension repository includes:
- Complete documentation
- All command files
- Configuration templates
- MIT License
- Changelog
---

[Copilot]

Pull request overview

Adds the GitHub Issues Integration community extension to Spec Kit’s community catalog so users can discover/install it, and lists it in the README community extensions table.

Changes:

• Added a new github-issues entry to extensions/catalog.community.json (plus a catalog updated_at bump).
• Added “GitHub Issues Integration” to the Community Extensions table in README.md.

Show a summary per file

File	Description
README.md	Adds the new integration to the Community Extensions list for discoverability.
extensions/catalog.community.json	Registers the github-issues extension in the community catalog with metadata and requirements.

Copilot's findings

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comments suppressed due to low confidence (1)

extensions/catalog.community.json:690

• Per extensions/EXTENSION-PUBLISHING-GUIDE.md, new catalog entries should use the current timestamp for created_at and updated_at. This entry sets both to 2026-04-12T00:00:00Z (midnight), which doesn’t match the “current timestamp” requirement; please set these to the actual time of publication/update (and keep them in sync with the catalog update).

      "verified": false,
      "downloads": 0,
      "stars": 0,
      "created_at": "2026-04-12T00:00:00Z",
      "updated_at": "2026-04-12T00:00:00Z"

• Files reviewed: 2/2 changed files
• Comments generated: 1

[Copilot]

extensions/catalog.community.json timestamps should follow the Extension Publishing Guide: use the current timestamp when adding/updating entries and bump the top-level updated_at to the current time. The catalog updated_at here (2026-04-12T12:06:00Z) looks stale relative to when this PR is being merged/reviewed; please update it to the time of this change.

This issue also appears on line 686 of the same file.

Suggested change

	"updated_at": "2026-04-12T12:06:00Z",
	"updated_at": "2026-04-13T00:00:00Z",