Menu
Create a new CDN bundle for the browser package with specified features
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 | add-cdn-bundle |
| description | Create a new CDN bundle for the browser package with specified features |
| argument-hint | <feature-combo> (e.g., replay.logs.metrics, tracing.logs, tracing.replay.feedback.logs.metrics) |
This skill creates a new CDN bundle for the browser package that includes a specific combination of features.
The user provides a feature combination using dot notation:
logs.metrics - Bundle with logs and metricsreplay.logs.metrics - Bundle with replay, logs, and metricstracing.replay.logs - Bundle with tracing, replay, and logstracing.replay.feedback.logs.metrics - Full featured bundleFeature order in bundle names: tracing → replay → feedback → logs → metrics
Follow the detailed guide at docs/adding-cdn-bundle.md to create the bundle.
Given a feature combination, derive these variants:
| Placeholder | Example (replay.logs.metrics) |
|---|---|
{FEATURE_COMBO} | replay.logs.metrics |
{feature_combo} | replay_logs_metrics |
{featureCombo} | replayLogsMetrics |
{Human Readable Features} | Replay, Logs, Metrics |
{Human Readable Feature List} | Replay, Logs, and Metrics |
packages/browser/src/index.bundle.{FEATURE_COMBO}.tspackages/browser/test/index.bundle.{FEATURE_COMBO}.test.tspackages/browser/rollup.bundle.config.mjs.size-limit.jsdev-packages/browser-integration-tests/package.jsondev-packages/browser-integration-tests/utils/generatePlugin.ts.github/workflows/build.ymlAfter making changes:
yarn lint
cd packages/browser && yarn build:dev
cd packages/browser && yarn test
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".
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.
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