Menu
Use when creating git commits - enforces conventional commit format with correct type prefixes for release-triggering vs non-release changes
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | commit |
| description | Use when creating git commits - enforces conventional commit format with correct type prefixes for release-triggering vs non-release changes |
<type>[(scope)]: <description>
init, deploy, cli-core, deps, ci)These types generate changesets and trigger npm releases:
| Type | Bump | Use for |
|---|---|---|
feat | minor | New commands, flags, features |
fix | patch | Bug fixes, crash fixes, incorrect output |
perf | patch | Performance improvements |
revert | patch | Reverting previous changes |
feat! / fix! | major | Breaking changes (removed commands, changed flag behavior) |
These do not trigger releases or changesets:
| Type | Use for |
|---|---|
chore | Tooling, build config, dependency updates |
refactor | Code restructuring without behavior change |
test | Adding or updating tests |
docs | Documentation only |
style | Formatting, whitespace |
build | Build system changes |
ci | CI/CD pipeline changes |
feat or fix! suffix (e.g., feat!)chore, refactor, test, etc.chore(deps) unless fixing a user-facing bug, then fix(deps)feat: auto-generate changesets from PR descriptions
feat(embeddings): add projection validation using groq-js
feat(cli): inject __SANITY_STAGING__ global in staging builds
fix(init): strip filename before counting nested folders in import path
fix(deploy): stop spinner before returning from app lookup
refactor(cli-core): replace oclif ux.colorize with node:util styleText
refactor(cli): migrate from zod to zod/mini for smaller bundle size
chore: skip auto-generated changeset when one already exists
chore(ci): use squiggler-app bot as changeset commit author
chore(deps): update swc-tooling
Build features with the Sanity App SDK (@sanity/sdk-react). Use when adding components, fetching or editing Sanity content, or working with hooks like useDocuments, useDocument, useDocumentProjection, useEditDocument, or useQuery.
Build features with the Sanity App SDK (@sanity/sdk-react) and Sanity UI. Use when adding components, fetching or editing Sanity content, or working with hooks like useDocuments, useDocument, useDocumentProjection, useEditDocument, or useQuery.
Use when writing, adding, or modifying e2e tests for CLI commands in packages/@sanity/cli-e2e/. Triggers on e2e test creation, new command test coverage, or changes to CLI test infrastructure.
Use this for writing or reviewing Sanity product UI copy: Studio UI text, error/validation messages, empty states, tooltips, buttons, status/confirmation dialogs, onboarding flows, CLI output, and API error responses. Trigger whenever you see UX writing, product copy, or interface text for Sanity (Studio, CLI, API), especially errors or system messages.