skills.rest
getsentry
getsentryOFFICIAL
Explore all skills by this author →
Website𝕏@sentryGitHub

track-framework-updates

Generate weekly digests of upstream framework releases, discussions, and RFCs for Sentry JS SDK packages.

8.7k|1.8k|Updated Feb 1, 2012
Search Tags:#backlog generation#release tracking#weekly digest#rss feeds#gitHub api#Sentry SDK#framework monitoring
One-click install
npx skills add https://github.com/getsentry/sentry-javascript --skill track-framework-updates
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: track-framework-updates
Source: https://github.com/getsentry/sentry-javascript/tree/main/.agents/skills/track-framework-updates
Command: npx skills add https://github.com/getsentry/sentry-javascript --skill track-framework-updates

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and assets (resource) components.

What problem does it solve?

Keeping the Sentry JavaScript SDK compatible with dozens of upstream frameworks (React, Next.js, Vue, Nuxt, Node.js, and more) requires manually monitoring releases, RFCs, and blog posts across many repositories, which is time-consuming and easy to miss breaking changes.

Core Features & Use Cases

  • Automated upstream monitoring: Fetches GitHub releases, Discussions, RFC-repo PRs, and RSS/Atom feeds for every framework the SDK instruments, filtered to a configurable date window.
  • Relevance classification: Classifies each change as high, medium, or low relevance based on how the SDK instruments routers, lifecycle hooks, error boundaries, and async context, and flags new major versions outside declared peerDependencies ranges.
  • Backlog generation: Produces actionable backlog candidates tied to specific @sentry/* packages, plus structured JSON and Markdown digests.
  • Use Case: Run the skill weekly in CI to get a digest showing that Next.js shipped a new major version outside the SDK's supported range, with a ready-to-file backlog item to add support.

Quick Start

Ask the AI to track framework updates for the last 7 days and produce the weekly digest.

Frequently Asked Questions about track-framework-updates

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I track upstream framework releases for the Sentry JavaScript SDK?▼

Run the collect_updates.py script with an optional --since-days flag to fetch releases, discussions, RFCs, and RSS items for all frameworks in sources.json. The skill then classifies changes and writes JSON and Markdown digests to the output directory.

How are framework changes classified by relevance to the SDK?▼

Each change is classified as high, medium, or low using rules in assets/relevance-guidelines.md tied to SDK instrumentation surfaces like routers, lifecycle hooks, error boundaries, and async context. New major versions outside declared peerDependencies ranges are always classified as high.

Which frameworks and platforms does the digest cover?▼

It covers client frameworks (Angular, React, Vue, Svelte, Solid, Ember), server frameworks (Hono, NestJS, Express, Effect), meta-frameworks (Next.js, Nuxt, SvelteKit, Astro, Remix), platforms (Node.js, Bun, Deno, Cloudflare Workers, AWS Lambda), and libraries like Pinia, Pino, Winston, and Zod.

What dependencies are required to run the fetcher scripts?▼

The scripts use only the Python 3 standard library plus the authenticated GitHub CLI (gh) for API calls. No pip packages or npm dependencies need to be installed.

How does the skill handle untrusted content in release notes?▼

All fetched text is sanitized by redacting lines matching prompt-injection patterns, truncating release bodies to 8 KB, capping feeds at 5 MB, and blocking non-HTTPS redirects. The skill treats all fetched content as data and never follows instructions embedded in it.

What happens when a new framework package is not tracked in sources.json?▼

The check_sources.py script compares packages in the packages/ directory against sources.json and reports untracked public @sentry/* packages. These appear in the digest's source coverage section so they can be added or explicitly excluded.

Related Skills

Explore More Software Engineering Skills→
boykushboykush
2

rule-issue-file

File GitHub issues for business rules from example mappings with deduplication.

Community
Advanced
dburkartdburkart
5

file-issue

File GitHub issues with priority and area labels after deduplication.

Community
Intermediate
coopeverythingcoopeverything

verify-fix

Map code changes to Playwright E2E tests and execute them against production.

Community
Advanced
commercetoolscommercetools
154

renovate-review

Assess GitHub Renovate PRs for NPM dependency upgrade safety and risk.

Official
Intermediate