メニュー
Upgrade a dependency in the Sentry JavaScript SDK. Use when upgrading packages, bumping versions, or fixing security vulnerabilities via dependency updates.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
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.
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
Help the user draft and (with their explicit approval) post a status update to a Linear project they lead. Use whenever the user wants to "post a project update", "write a status update", "update my Linear project", "send a project update", or asks for help with weekly/biweekly project updates. Also trigger when the user pastes a Linear project URL and asks for an update, mentions wanting to write an update for their project, or wants help drafting a status message for stakeholders. Even when the user doesn't explicitly say "post" or "status update" — if the underlying request is "help me write an update for my Linear project", trigger this skill. The user always keeps final control of the words; this skill drafts a proposal and never posts without explicit confirmation in the same turn.
Analyze a Linear project's health and produce a status summary for a project lead or manager. Inspects status-update cadence, lead/owner presence, target-date realism and stability, issue staleness, milestone health, and scope creep. Use whenever the user wants a status report, project review, health check, weekly review, or audit of a Linear project — including phrases like "how is project X going", "give me a status on this Linear project", "audit this project", "is this project on track", "check project health", or when they paste a Linear project URL and ask for a summary. Use it even when the user doesn't explicitly say "audit" or "status" — if the request is fundamentally "tell me how this Linear project is doing", trigger this skill.
| 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> |
Only upgrade one package at a time.
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.
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:
yarn info <package-name>@<version> 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).
yarn install
yarn build:dev
yarn dedupe-deps:fix
yarn fix
yarn circularDepCheck
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