Add Spec Switcher extension to community catalog - #3935
Open
MannXo wants to merge 1 commit into
Open
Conversation
Add switch extension submitted by @wagner-sousa to: - extensions/catalog.community.json (alphabetical order) - docs/community/extensions.md community extensions table Closes github#3932
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 the
switchextension (Spec Switcher) to the community catalog, per the submission in #3932.Validation
extension.ymlmanifest presentschema_version: "1.0"v1.0.0, tagged 2026-08-01archive/refs/tags/v1.0.0.zip, 9 files^[a-z][a-z0-9-]*$switch1.0.0The manifest inside the v1.0.0 archive declares
version: 1.0.0,id: switch,speckit_version: ">=0.4.0"and two commands with no hooks, which is what the catalog entry records.One thing worth flagging rather than silently resolving: the repository's default branch is already at
1.1.0in bothextension.ymland the CHANGELOG, but nov1.1.0release or tag exists. This entry follows the releasedv1.0.0artifact, matching the submission. If @wagner-sousa cuts av1.1.0release, that is a follow-up update issue.categoryisprocessandeffectisread-write, sinceswitch.setrunsgit checkoutand, with--local-only, writes.specify/feature.json. That matches how the comparable worktree extensions are classified.Testing
The CLI reads the catalog over HTTP from
main, so the new entry cannot resolve locally until this merges. Serving the edited file and pointingSPECKIT_CATALOG_URLat it confirms the entry parses and renders end to end:I read the two command files and the README in the released archive. They are prompt markdown with no scripts;
switch.setblocks on a dirty working tree and does not writefeature.jsonoutside--local-only. Per the note at the top of the community extensions page, this is a completeness and formatting check, not an endorsement or an audit of the extension code.Closes #3932
cc @wagner-sousa
AI disclosure, per CONTRIBUTING.md: this PR was written with Claude Code. The catalog entry, docs row and PR text were AI-generated; the validation above was run against the live repository and release, and I reviewed the results.