メニュー
Create a new CDN bundle for the browser package with specified features
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 | 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