القائمة
Publish a new Sentry JavaScript SDK release. Use when preparing a release, updating the changelog, or creating a release branch.
التثبيت باستخدام 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 | 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"] |
See docs/publishing-a-release.md for full details.
develop with latest changes. Stash any unsaved work with git stash -u if needed.yarn changelog (use yarn changelog | pbcopy to copy output).CHANGELOG.md for the current version.prepare-release/VERSION off develop.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.meta(changelog): Update changelog for VERSIONmaster.git stash pop if needed.Follow docs/new-sdk-release-checklist.md. If anything doesn't match the checklist, remind the user.
yarn changelog — generate changelog entriesyarn lint — verify code qualityyarn test — run test suiteyarn build:dev — verify build