chore(skills): Add bump-conventions skill

Co-Authored-By: Opus 4.8 <noreply@anthropic.com>

Author: andreiborza

.agents/skills/bump-conventions/SKILL.md

@@ -0,0 +1,88 @@
+---
+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"
+---
+
+# Bump `@sentry/conventions`
+
+Bump `@sentry/conventions` across every `package.json` at once, keeping the two pin styles consistent, then refresh `yarn.lock`.
+
+## 1. Determine the target version
+
+If the user gave a version, use it. Otherwise:
+
+```bash
+npm view @sentry/conventions version
+```
+
+Find the current version to replace:
+
+```bash
+grep -rhoE '"@sentry/conventions": "[^"]+"' --include=package.json --exclude-dir=node_modules packages dev-packages | sort -u
+```
+
+You should see exactly two entries for the current version:
+
+- `"@sentry/conventions": "^0.15.1"`, caret range in `packages/*` `dependencies`
+- `"@sentry/conventions": "0.15.1"`, exact pin in `dev-packages/*` `devDependencies`
+
+**Preserve each style.** Runtime packages keep the caret; dev-package test suites keep the exact pin. If you see more than two distinct entries, list them and confirm with the user before proceeding.
+
+## 2. Update every `package.json`
+
+Replace both forms in one pass. With `OLD` and `NEW` set to the bare versions (e.g. `0.15.1` and `0.16.0`):
+
+```bash
+grep -rl '"@sentry/conventions"' --include=package.json --exclude-dir=node_modules packages dev-packages \
+  | xargs sed -i '' \
+    -e "s/\"@sentry\/conventions\": \"\^${OLD}\"/\"@sentry\/conventions\": \"^${NEW}\"/" \
+    -e "s/\"@sentry\/conventions\": \"${OLD}\"/\"@sentry\/conventions\": \"${NEW}\"/"
+```
+
+> `--exclude-dir=node_modules` is required: without it the recursive grep walks installed dependencies and `sed` would rewrite `package.json` files inside `node_modules`.
+> `sed -i ''` is the BSD/macOS form. On Linux use `sed -i` (no `''`).
+
+Verify every reference is now `NEW`, still split across the two styles:
+
+```bash
+grep -rhoE '"@sentry/conventions": "[^"]+"' --include=package.json --exclude-dir=node_modules packages dev-packages | sort | uniq -c
+```
+
+## 3. Refresh the lockfile and build
+
+```bash
+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:
+
+```bash
+grep -n '@sentry/conventions@' yarn.lock
+```
+
+## 4. Check for breaking API changes
+
+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.
+
+## 5. Final verification
+
+```bash
+yarn circularDepCheck
+yarn fix
+yarn test
+```
+
+## Commit
+
+Use the `feat(deps):` prefix the repo uses for dependency bumps:
+
+```
+feat(deps): Bump `@sentry/conventions` to <NEW>
+```
+
+Follow the repo's commit and PR conventions (target `develop`, draft PR, `## What` / `## Why`). Do **not** create the commit yourself unless the user invokes `/commit-push-pr`.