Conversation
There was a problem hiding this comment.
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
issueentry toextensions/catalog.community.jsonpointing toaaronrsun/spec-kit-issuev1.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.
| | 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) | |
There was a problem hiding this comment.
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.
| | 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) | |
| "created_at": "2026-04-12T00:00:00Z", | ||
| "updated_at": "2026-04-12T00:00:00Z" |
There was a problem hiding this comment.
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.
| "updated_at": "2026-03-31T00:00:00Z" | ||
| }, | ||
| "issue": { | ||
| "name": "Issue Extension", |
There was a problem hiding this comment.
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.
| "name": "Issue Extension", | |
| "name": "Issues", |
mnriem
left a comment
mnriem
left a comment
There was a problem hiding this comment.
Please address Copilot feedback
#2175