move

Author: chargome

.agents/skills/release/SKILL.md

@@ -0,0 +1,31 @@
+---
+name: release
+description: Publish a new Sentry JavaScript SDK release. Use when preparing a release, updating the changelog, or creating a release branch.
+argument-hint: [VERSION]
+---
+
+# Release Process
+
+See `docs/publishing-a-release.md` for full details.
+
+## Steps
+
+1. Ensure you're on `develop` with latest changes. Stash any unsaved work with `git stash -u` if needed.
+2. Run `yarn changelog` (use `yarn changelog | pbcopy` to copy output).
+3. Decide on a version per [semver](https://semver.org). Check the top of `CHANGELOG.md` for the current version.
+4. Create branch `prepare-release/VERSION` off `develop`.
+5. Update `CHANGELOG.md` — add the new version entry with the changelog output. See the "Updating the Changelog" section in `docs/publishing-a-release.md` for formatting details. Do not remove existing entries.
+6. Commit: `meta(changelog): Update changelog for VERSION`
+7. Push the branch and remind the user to open a PR targeting `master`.
+8. If you were on a different branch, checkout back and `git stash pop` if needed.
+
+## First-time SDK releases
+
+Follow `docs/new-sdk-release-checklist.md`. If anything doesn't match the checklist, remind the user.
+
+## Key commands
+
+- `yarn changelog` — generate changelog entries
+- `yarn lint` — verify code quality
+- `yarn test` — run test suite
+- `yarn build:dev` — verify build

.agents/skills/upgrade-dep/SKILL.md

@@ -0,0 +1,58 @@
+---
+name: upgrade-dep
+description: Upgrade a dependency in the Sentry JavaScript SDK. Use when upgrading packages, bumping versions, or fixing security vulnerabilities via dependency updates.
+argument-hint: <package-name>
+---
+
+# Dependency Upgrade
+
+**Only upgrade one package at a time.**
+
+## Upgrade command
+
+```bash
+npx yarn-update-dependency@latest [package-name]
+```
+
+If the dependency is not defined in any `package.json`, run the upgrade from the root workspace (the `yarn.lock` lives there).
+
+Avoid upgrading top-level dependencies (especially test dependencies) without asking the user first.
+
+Ensure updated `package.json` files end with a newline.
+
+## OpenTelemetry constraint
+
+**STOP** if upgrading any `opentelemetry` package would introduce forbidden versions:
+- `2.x.x` (e.g., `2.0.0`)
+- `0.2xx.x` (e.g., `0.200.0`, `0.201.0`)
+
+Verify before upgrading:
+
+```bash
+yarn info <package-name>@<version> dependencies
+```
+
+## E2E test dependencies
+
+Do **not** upgrade the major version of a dependency in `dev-packages/e2e-tests/test-applications/*` if the test directory name pins a version (e.g., `nestjs-8` must stay on NestJS 8).
+
+## Post-upgrade verification
+
+```bash
+yarn install
+yarn build:dev
+yarn dedupe-deps:fix
+yarn fix
+yarn circularDepCheck
+```
+
+## Useful commands
+
+```bash
+yarn list --depth=0          # Check dependency tree
+yarn why [package-name]      # Find why a package is installed
+yarn info <pkg> dependencies # Inspect package dependencies
+yarn info <pkg> versions     # Check available versions
+yarn outdated                # Check outdated dependencies
+yarn audit                   # Check for security vulnerabilities
+```

.agents/skills/upgrade-otel/SKILL.md

@@ -0,0 +1,32 @@
+---
+name: upgrade-otel
+description: Upgrade OpenTelemetry instrumentations across the Sentry JavaScript SDK. Use when bumping OTel instrumentation packages to their latest versions.
+argument-hint: ""
+---
+
+# Upgrading OpenTelemetry Instrumentations
+
+**All upgrades must be free of breaking changes.** Read each changelog before proceeding.
+
+## 1. `packages/**`
+
+Upgrade in this order:
+
+1. **`@opentelemetry/instrumentation`** to latest. Check changelog: `https://github.com/open-telemetry/opentelemetry-js/blob/main/experimental/CHANGELOG.md`
+2. **All `@opentelemetry/instrumentation-*` packages.** Check each changelog: `https://github.com/open-telemetry/opentelemetry-js-contrib/blob/main/packages/instrumentation-{name}/CHANGELOG.md`
+3. **Third-party instrumentations** (currently `@prisma/instrumentation`). Check their changelogs.
+
+**STOP** if any upgrade introduces breaking changes — fail with the reason.
+
+## 2. `dev-packages/**`
+
+- If an app depends on `@opentelemetry/instrumentation` >= `0.200.x`, upgrade to latest.
+- If an app depends on `@opentelemetry/instrumentation-http` >= `0.200.x`, upgrade to latest.
+
+Same rule: no breaking changes allowed.
+
+## 3. Regenerate lock file
+
+```bash
+yarn install
+```