Repository navigation
chore(release): version packages - #2258
Merged
Merged
Conversation
openspec-release-bot
Bot
requested review from
alfred-openspec
and removed request for
a team
November 17, 2026 00:38
Contributor
|
Important Review skippedBot user detected. To trigger a single review, invoke the
|
Contributor
No PR-relevant drift confirmed.
|
clay-good
self-requested a review
November 17, 2026 00:55
clay-good
approved these changes
Nov 17, 2026
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@fission-ai/openspec@2.1.0
Minor Changes
#2241
ee9038aThanks @clay-good! - # OpenSpec now supports global skills for coding agentsAs more teams adopt Vercel’s
skillsinstaller, it’s becoming a common way to install skills across coding tools. OpenSpec is adopting it too, so we can spend less time maintaining installer code and more time improving the skills themselves.Moving to Vercel’s installer gives OpenSpec native support for global skill installation. Your coding agent can use the same OpenSpec skills across projects. Vercel’s installer handles the location for each supported agent, whether it reads
~/.agents/skills/or uses its own folder.What you’ll see when you upgrade
With the new CLI, the next time you run
openspec updatefrom a repo that has its own OpenSpec skills, you’ll see this choice:Nothing changes until you choose. In CI or from an agent there is no question: update refreshes the skills where they are.
Keep in this project
Press Enter. The skills stay in your repo.
openspec/config.yaml. It records your choice, so your teammates aren’t asked.Choose this if GitHub’s hosted Copilot agent reads the skills from the repo. You can switch later with
openspec init --scope global.Switch to global
We recommend this for most teams. The skills are installed globally on your machine, and the copies in the repo are removed.
openspec update, and answers Yes when it offers to set up skills on their machine.In a script, run
openspec init --tools <ids>in place of step 2. Upgrade everyone’s CLI before you switch a repo: earlier versions only know project skills.If a script sets up your repos
In 2.0,
openspec init --tools claudein a new repo wrote the skills into that repo. It now installs them globally. To keep them in your project repo, add--scope project:Existing repos don’t change until someone answers the question above.
Before you update
openspec update --dry-runshows what will change.npx skills add? Keep that install and runopenspec update.The upgrade guide has the same steps on one page.