Added issues extension

[aaronrsun]

#2175

[Copilot]

Pull request overview

Adds a new community extension entry for importing/syncing Spec Kit artifacts from GitHub Issues, and exposes it in the root community extensions list.

Changes:

• Add “Issues” extension row to the Community Extensions table in README.md.
• Add a new issue entry to extensions/catalog.community.json pointing to aaronrsun/spec-kit-issue v1.0.0.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

File	Description
README.md	Adds the extension to the public-facing community extensions table.
extensions/catalog.community.json	Registers the new extension’s metadata in the community catalog.

---

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

[mnriem]

Please address Copilot feedback

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 4 comments.

---

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

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

---

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

[aaronrsun]

Please address Copilot feedback

@mnriem Done. Please review again.

[Copilot]

Pull request overview

Registers a new community extension for generating/syncing local specs from GitHub Issues, and updates the root README’s community extension list accordingly.

Changes:

• Add a new issue extension entry to the community extensions catalog.
• Rename the existing github-issues extension display name and update the README to list both integrations.

Show a summary per file

File	Description
extensions/catalog.community.json	Adds a new GitHub Issues-related extension entry and renames the existing GitHub Issues integration’s display name.
README.md	Updates the community extensions table to include the new GitHub Issues extension and reflect the renamed existing one.

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:760

• The new extension uses id: "issue" and the display name "GitHub Issues Integration 2". With two GitHub Issues-related entries, a generic ID and numbered name make it difficult to distinguish in specify extension search output and docs. Consider using a more specific ID (likely aligned to the repo/manifest, e.g., github-issue/github-issues-sync) and a descriptive name without numbering (e.g., include the author or the key differentiator like "Issue→Spec Sync").

    "issue": {
      "name": "GitHub Issues Integration 2",
      "id": "issue",
      "description": "Creates and syncs local specs based on an existing issue in GitHub",
      "author": "aaronrsun",

• Files reviewed: 2/2 changed files
• Comments generated: 0 new

[mnriem]

Thank you!