Skip to content

Added issues extension #2194

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
aaronrsun wants to merge 1 commit into
base: main
Choose a base branch
from
+25 −0
Open

Added issues extension #2194

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -199,6 +199,7 @@ The following community-contributed extensions are available in [`catalog.commun
| Fix Findings | Automated analyze-fix-reanalyze loop that resolves spec findings until clean | `code` | Read+Write | [spec-kit-fix-findings](https://github.com/Quratulain-bilal/spec-kit-fix-findings) |
| FixIt Extension | Spec-aware bug fixing — maps bugs to spec artifacts, proposes a plan, applies minimal changes | `code` | Read+Write | [spec-kit-fixit](https://github.com/speckit-community/spec-kit-fixit) |
| Fleet Orchestrator | Orchestrate a full feature lifecycle with human-in-the-loop gates across all SpecKit phases | `process` | Read+Write | [spec-kit-fleet](https://github.com/sharathsatish/spec-kit-fleet) |
| Issues | Creates and syncs local specs based on an existing issue in GitHub | `integration` | Read+Write | [spec-kit-issue](https://github.com/aaronrsun/spec-kit-issue) |
Copy link

Copilot AI Apr 12, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The extension name is inconsistent between README ("Issues") and the community catalog entry ("Issue Extension"). Please align the displayed name across both places (and ideally with the upstream extension’s own name) to avoid confusion when users search/install.

Suggested change
| Issues | Creates and syncs local specs based on an existing issue in GitHub | `integration` | Read+Write | [spec-kit-issue](https://github.com/aaronrsun/spec-kit-issue) |
| Issue Extension | Creates and syncs local specs based on an existing issue in GitHub | `integration` | Read+Write | [spec-kit-issue](https://github.com/aaronrsun/spec-kit-issue) |

Copilot uses AI. Check for mistakes.
| Iterate | Iterate on spec documents with a two-phase define-and-apply workflow — refine specs mid-implementation and go straight back to building | `docs` | Read+Write | [spec-kit-iterate](https://github.com/imviancagrace/spec-kit-iterate) |
| Jira Integration | Create Jira Epics, Stories, and Issues from spec-kit specifications and task breakdowns with configurable hierarchy and custom field support | `integration` | Read+Write | [spec-kit-jira](https://github.com/mbachorik/spec-kit-jira) |
| Learning Extension | Generate educational guides from implementations and enhance clarifications with mentoring context | `docs` | Read+Write | [spec-kit-learn](https://github.com/imviancagrace/spec-kit-learn) |
Expand Down
24 changes: 24 additions & 0 deletions extensions/catalog.community.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -649,6 +649,30 @@
"created_at": "2026-03-06T00:00:00Z",
"updated_at": "2026-03-31T00:00:00Z"
},
"issue": {
"name": "Issue Extension",
Copy link

Copilot AI Apr 12, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Consider making the catalog "name" match the README table entry (and the extension’s branding). Right now it’s "Issue Extension" here while README lists "Issues", which can make catalog search results and docs references inconsistent.

Suggested change
"name": "Issue Extension",
"name": "Issues",

Copilot uses AI. Check for mistakes.
"id": "issue",
"description": "Creates and syncs local specs based on an existing issue in GitHub",
"author": "aaronrsun",
"version": "1.0.0",
"download_url": "https://github.com/aaronrsun/spec-kit-issue/archive/refs/tags/v1.0.0.zip",
"repository": "https://github.com/aaronrsun/spec-kit-issue",
"homepage": "https://github.com/aaronrsun/spec-kit-issue",
"documentation": "https://github.com/aaronrsun/spec-kit-issue/blob/main/README.md",
"changelog": "https://github.com/aaronrsun/spec-kit-issue/blob/main/CHANGELOG.md",
"license": "MIT",
"requires": {
"speckit_version": ">=0.1.0"
},
"tags": [
"issue"
],
"verified": false,
"downloads": 0,
"stars": 0,
"created_at": "2026-04-12T00:00:00Z",
"updated_at": "2026-04-12T00:00:00Z"
Comment on lines +673 to +674
Copy link

Copilot AI Apr 12, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The new catalog entry sets created_at/updated_at to midnight ("...T00:00:00Z") and the top-level "updated_at" field in this file was not bumped. The Extension Publishing Guide asks to use the current timestamp for created_at/updated_at and to update the top-level updated_at whenever the catalog changes.

Copilot uses AI. Check for mistakes.
},
"iterate": {
"name": "Iterate",
"id": "iterate",
Expand Down
Loading