Skip to content

chore(release): version packages - #2258

Merged
clay-good merged 1 commit into
mainfrom
changeset-release/main
Nov 17, 2026
Merged

clay-good merged 1 commit into
mainfrom
changeset-release/main

Conversation

@openspec-release-bot

Copy link
Copy Markdown
Contributor

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 ee9038a Thanks @clay-good! - # OpenSpec now supports global skills for coding agents

    As more teams adopt Vercel’s skills installer, 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 update from a repo that has its own OpenSpec skills, you’ll see this choice:

    Where should OpenSpec keep this project’s skills?
    
    ❯ Keep in this project   Keep the skills in this repo.
      Switch to global       Install the skills globally, for every project on this machine.
    

    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.

    1. Commit 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.

    1. Commit the removed files.
    2. Each teammate pulls, runs 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 claude in a new repo wrote the skills into that repo. It now installs them globally. To keep them in your project repo, add --scope project:

    openspec init --scope project --tools claude

    Existing repos don’t change until someone answers the question above.

    Before you update

    • Edited a built-in skill? Update replaces the built-in skill folders. Save your edits first, along with any file you added inside one. openspec update --dry-run shows what will change.
    • Git. Installing or refreshing skills needs Git and access to GitHub.
    • Node. An npm install needs Node 22.20.0 or newer. The standalone executable needs nothing.
    • Already ran npx skills add? Keep that install and run openspec update.

    The upgrade guide has the same steps on one page.

@openspec-release-bot
openspec-release-bot Bot requested a review from a team as a code owner November 17, 2026 00:38
@openspec-release-bot
openspec-release-bot Bot requested review from alfred-openspec and removed request for a team November 17, 2026 00:38
@coderabbitai

coderabbitai Bot commented Nov 17, 2026

Copy link
Copy Markdown
Contributor

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

@openspec-cloud

Copy link
Copy Markdown
Contributor

No PR-relevant drift confirmed.

AI-generated · A citation proves the line exists, not that it makes the case — verify before acting.
Checked the 0 requirements selected for this PR at 552c63d (322 total).
This is not a full-repository clean result; see the check for coverage and any broader findings.
View results · Click Refresh, then Scan again in the check. Or comment /openspec-cloud.

@clay-good
clay-good self-requested a review November 17, 2026 00:55
@clay-good
clay-good added this pull request to the merge queue Nov 17, 2026
Merged via the queue into main with commit 8bd4b35 Nov 17, 2026
35 checks passed
@clay-good
clay-good deleted the changeset-release/main branch November 17, 2026 01:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant