feat: add GitHub Issues Integration to community catalog#2188
feat: add GitHub Issues Integration to community catalog#2188mnriem merged 4 commits intogithub:mainfrom
Conversation
Add GitHub Issues Integration extension to the community catalog and README. Extension provides: - /speckit.github-issues.import - Import GitHub Issue and generate spec.md - /speckit.github-issues.sync - Keep specs updated with issue changes - /speckit.github-issues.link - Add bidirectional traceability Resolves github#2175
There was a problem hiding this comment.
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-issuesentry toextensions/catalog.community.json(plus a catalogupdated_atbump). - 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 forcreated_atandupdated_at. This entry sets both to2026-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
mnriem
left a comment
There was a problem hiding this comment.
Please address Copilot feedback
Updated timestamps for created_at and updated_at fields.
The Copilot feedback has been addressed and I have updated the timestamps. |
There was a problem hiding this comment.
Pull request overview
Adds the GitHub Issues Integration community extension to Spec Kit’s community catalog so users can install it via the catalog and discover it in the README list.
Changes:
- Added a new
github-issuesentry toextensions/catalog.community.json(includingrequires.toolsforgh). - Updated the community catalog top-level
updated_attimestamp. - Added the extension to the Community Extensions table in
README.md.
Show a summary per file
| File | Description |
|---|---|
| README.md | Adds “GitHub Issues Integration” to the Community Extensions table for discoverability. |
| extensions/catalog.community.json | Registers the new github-issues extension in the community catalog and updates catalog metadata timestamps. |
Copilot's findings
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 2/2 changed files
- Comments generated: 2
|
Thank you! |
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
github-issuesintegrationFeatures
/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 issuesProblem Solved
Developers already document requirements in GitHub Issues but then rewrite everything from
scratch in
spec.mdwhen starting SDD. This extension eliminates that duplicate work by:Installation