Sanity Studio Upgrade

by sanity-io88d6cdfa7cb0No licenseListed Oct 8, 2026Updated Oct 8, 2026

Produces a tailored Sanity Studio upgrade plan by inspecting the repository's installed versions, config, and source, then reporting only the breaking changes that actually apply. Covers Studio v3 and later; v2 projects are identified and redirected, not planned. Use this skill whenever someone wants to upgrade, migrate, or modernize a Sanity Studio across one or more major versions from v3 onward, asks what will break if they bump the `sanity` package, asks why their Studio broke after an upgrade, or asks how far behind their Studio is. Triggers on "upgrade sanity studio", "migrate our studio to v6", "bump sanity", "what breaks if we upgrade", "our studio is on an old version", "sanity upgrade plan", "is our studio out of date", "we are several majors behind". DO NOT load for upgrading non-Sanity dependencies, for Content Lake `apiVersion` questions, for content or schema migrations that change documents, or for setting up a new Sanity project.

Only the file list is public. File contents are available once the skill is installed in a workspace.

PathSizeType
references/boundaries.md4.8 KBtext/markdown
references/boundary.v4.md5.9 KBtext/markdown
references/boundary.v5.md7.2 KBtext/markdown
references/boundary.v6.md7.7 KBtext/markdown
references/deprecations.md2.5 KBtext/markdown
references/detect.md14.7 KBtext/markdown
references/package-coupling.md14.6 KBtext/markdown
references/plugins.md23.3 KBtext/markdown
references/report-template.md17.2 KBtext/markdown
references/version-lookup.md18.9 KBtext/markdown
SKILL.md19 KBtext/markdown

Source and attribution

Source:sanity-io/agent-toolkitinskills/sanity-studio-upgradeat commit88d6cdf

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal