Menu
Bump the @sentry/conventions dependency to a new version across every package in the monorepo. Use when upgrading, bumping, or aligning @sentry/conventions, or when a new @sentry/conventions release needs to be pulled into all workspaces.
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
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
Produce a weekly digest of upstream framework/library activity (releases, Discussions, RFCs, RSS) for the Sentry JS SDK. Use when asked to "track framework updates", "check framework releases", "what changed upstream", "weekly framework digest", "what's new in React/Next/Nuxt/etc.", or to surface backlog candidates from upstream frameworks. Do NOT use for checking Sentry SDK releases, internal package updates, or individual bug triage.
Backport a merged PR to a maintenance major branch (v10 by default) in getsentry/sentry-javascript. Cherry-picks the PR's squash-merge commit onto the target branch, namespaces the commit/PR title scope (e.g. fix(core) -> fix(v10/core)), and opens a draft backport PR. Use when asked to backport a PR, or port a fix to v10 (or an older major like v9). Trigger phrases include "backport", "port to v10", "release this on v10".
Write high-quality unit tests (Vitest) and E2E tests (Playwright) following senior test-engineering practices. Use this skill whenever asked to write tests, add test coverage, create test cases, fix failing tests, add missing assertions, test a new feature, write specs, or cover edge cases. Also trigger when the user says "write tests for", "add tests", "test this", "cover this", "needs tests", "add E2E test", "add unit test", "test coverage", or when reviewing code and noticing missing test coverage.
Analyze and propose fixes for Dependabot security alerts
Triage GitHub issues with codebase research and actionable recommendations
| name | bump-conventions |
| description | Bump the @sentry/conventions dependency to a new version across every package in the monorepo. Use when upgrading, bumping, or aligning @sentry/conventions, or when a new @sentry/conventions release needs to be pulled into all workspaces. |
| argument-hint | [version] # e.g. 0.16.0; defaults to latest on npm |
@sentry/conventionsBump @sentry/conventions across every package.json at once, keeping the two pin styles consistent, then refresh yarn.lock.
If the user gave a version, use it. Otherwise get the latest:
npm view @sentry/conventions version
Find every package.json that declares @sentry/conventions (use the Grep tool so node_modules and build output are skipped automatically) and bump each to the new version. There are two pin styles, and each must keep its style:
packages/* declare a caret range in dependencies, e.g. "^0.15.1" → "^0.16.0"dev-packages/* test suites declare an exact pin in devDependencies, e.g. "0.15.1" → "0.16.0"Edit only the version string; leave the caret alone. If a file declares a version that matches neither the current caret nor the exact pin, list it and confirm with the user before touching it. Preserve each file's trailing newline.
yarn install
yarn dedupe-deps:fix
yarn build:dev
yarn install collapses the combined yarn.lock entry ("@sentry/conventions@<OLD>", "@sentry/conventions@^<OLD>":) onto the new version. Confirm no stale <OLD> resolution remains:
grep -n '@sentry/conventions@' yarn.lock
A conventions bump can rename or remove exported attribute constants. If yarn build:dev fails, inspect the type errors and update usages in src/ and test/. Heaviest consumers: packages/core, packages/opentelemetry, packages/aws-serverless.
Use LSP findReferences on the changed export to catch every call site. Do not paper over a rename with a cast.
After fixing, re-run yarn build:dev and confirm it passes before verifying, so the next step runs against fresh build output.
yarn circularDepCheck
yarn fix
yarn test
Use the chore(deps): prefix the repo uses for dependency bumps:
chore(deps): Bump `@sentry/conventions` to <NEW>