chore(catalog): add Jira Integration (Sync Engine) extension#2895
Open
ashbrener wants to merge 2 commits into
Open
chore(catalog): add Jira Integration (Sync Engine) extension#2895ashbrener wants to merge 2 commits into
ashbrener wants to merge 2 commits into
Conversation
Adds a new community-catalog listing for `spec-kit-jira-sync` (ashbrener/spec-kit-jira-sync), a reconcile-engine bridge that mirrors spec-kit specs into Jira (Epic per repo, Story per spec, Subtask per phase): idempotent, drift-aware, fail-closed. Catalog id is `jira-sync` because the `jira` id is already taken by an unrelated extension; display name "Jira Integration (Sync Engine)" disambiguates from the existing "Jira Integration" listing. Touches the two catalog surfaces: 1. extensions/catalog.community.json - the new "jira-sync" entry, inserted after the existing "jira" entry. Field shape matches the sibling "linear" entry exactly. 2. docs/community/extensions.md - the table row, after the existing Jira Integration row. JSON validated; diff is the single entry + the one table row.
Contributor
There was a problem hiding this comment.
Pull request overview
Note
Copilot was unable to run its full agentic suite in this review.
Adds a new community extension entry for a Jira sync/reconcile engine and documents it in the community extensions list.
Changes:
- Added
jira-syncmetadata to the community extensions catalog - Added
Jira Integration (Sync Engine)to the community extensions documentation table
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| extensions/catalog.community.json | Registers the new jira-sync extension (metadata, links, tags, requirements). |
| docs/community/extensions.md | Lists the new extension in the community extensions table for discoverability. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| "jira-sync": { | ||
| "name": "Jira Integration (Sync Engine)", | ||
| "id": "jira-sync", | ||
| "description": "A real reconcile engine — idempotent, drift-aware, fail-closed — that mirrors spec-kit specs into Jira (Epic per repo, Story per spec, Subtask per phase) and never corrupts your board.", |
| | Intelligent Agent Orchestrator | Cross-catalog agent discovery and intelligent prompt-to-command routing | `process` | Read+Write | [spec-kit-orchestrator](https://github.com/pragya247/spec-kit-orchestrator) | | ||
| | 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) | | ||
| | Jira Integration (Sync Engine) | A real reconcile engine — idempotent, drift-aware, fail-closed — that mirrors spec-kit specs into Jira (Epic per repo, Story per spec, Subtask per phase) and never corrupts your board | `integration` | Read+Write | [spec-kit-jira-sync](https://github.com/ashbrener/spec-kit-jira-sync) | |
…opilot review)
Drop the comparative/absolute framing ('A real …', 'never corrupts your board')
flagged by Copilot; keep the factual, tested capability descriptors (idempotent,
drift-aware, fail-closed). Applies to both the catalog entry and the docs table row.
Contributor
Author
|
Thanks @copilot-pull-request-reviewer — addressed both comments in |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a community-catalog listing for
spec-kit-jira-sync— a real reconcile-engine bridge that mirrors spec-kit specs into Jira (Epic per repo, Story per spec, Subtask per phase): idempotent, drift-aware, fail-closed — unlike prompt extensions that ask an agent to POST to Jira.Catalog id is
jira-sync(thejiraslot is taken by an unrelated extension); display name "Jira Integration (Sync Engine)" disambiguates from the existing "Jira Integration" listing.Touches the two catalog surfaces:
extensions/catalog.community.json— the newjira-syncentry (field shape matches the siblinglinearentry).docs/community/extensions.md— the table row.JSON validated. Release: https://github.com/ashbrener/spec-kit-jira-sync/releases/tag/v0.1.0 · License: MIT.