skills.rest
jellyrock
jellyrockOFFICIAL
Explore all skills by this author →
WebsiteGitHub

dep-major

Standardize major dependency bump reviews for JellyRock Roku applications.

37|2|Updated Jun 28, 2025
Search Tags:#code-review#dependency-management#renovate#jellyrock#roku#brightscript#major-version-bump
One-click install
npx skills add https://github.com/jellyrock/jellyrock --skill dep-major
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dep-major
Source: https://github.com/jellyrock/jellyrock/tree/main/.claude/skills/dep-major
Command: npx skills add https://github.com/jellyrock/jellyrock --skill dep-major

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Major dependency version bumps for the JellyRock Roku app often introduce runtime breaking changes that pass CI green checks but fail in real use, leading to inconsistent manual review processes and missed migration steps.

Core Features & Use Cases

  • Standardized Review Workflow: Applies a consistent SOP to all major dependency bumps, including grouped Renovate PRs that update multiple dependencies at once and manual major version bumps for individual packages.
  • Automated Breaking Change Analysis: Fetches upstream changelogs and migration guides, maps breaking changes to actual call sites in JellyRock's BrightScript and Node.js codebase, and surfaces required code changes.
  • Type-Appropriate Validation: Runs the correct validation gate for each dependency type (BrightScript build/device tests for runtime libraries, script tests for Node tooling, CI checks for GitHub Actions) and identifies latent breaks that CI does not cover.
  • Use Case: When a Renovate major PR updates the brighterscript build tool, this skill automatically pulls the changelog, finds all affected build configuration and source code call sites, runs the validate/build/lint gate, and produces a clear go/no-go verdict with migration steps for human review.

Quick Start

Use the dep-major skill to review Renovate major PR #456 for the roku-log runtime library and get a go/no-go verdict with any required migration steps.

Frequently Asked Questions about dep-major

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

FAQPage Schema
How do I review major dependency version bumps for BrightScript Roku apps?▼

Reviewing major dependency version bumps for BrightScript Roku apps requires fetching upstream changelogs, mapping breaking changes to local code call sites, and running type-appropriate validation gates to produce a go/no-go verdict with migration steps.

Why do major dependency updates pass CI but break Roku apps at runtime?▼

Major dependency updates pass CI but break Roku apps at runtime because standard CI pipelines miss runtime breaking changes in BrightScript libraries, requiring automated breaking change analysis and targeted validation gates to catch latent failures.

How do I handle grouped Renovate major PRs that update multiple dependencies at once?▼

Handling grouped Renovate major PRs with multiple dependencies involves applying a standardized review workflow that fetches changelogs for each package, maps breaking changes to call sites, and runs validation gates for BrightScript, Node.js, and GitHub Actions.

What validation gates should I run for different dependency types in a Roku project?▼

Validation gates for Roku project dependencies depend on type: BrightScript build and device tests for runtime libraries, script tests for Node.js build tooling, and CI checks for GitHub Actions workflows, ensuring type-appropriate coverage for major version bumps.

Can I use this dependency review workflow for manually initiated major version bumps?▼

Yes, this dependency review workflow supports both Renovate-generated major PRs and manually initiated major version bumps for runtime BrightScript libraries, Node.js build tooling, and GitHub Actions workflows used by the project.

What's the best way to map breaking changes from upstream changelogs to local BrightScript code?▼

Mapping breaking changes from upstream changelogs to local BrightScript code involves fetching migration guides, identifying affected build configuration and source code call sites, and surfacing required code changes with a go/no-go verdict for human review.

Related Skills

Explore More Software Engineering Skills→
shimabukuromegshimabukuromeg
1

renovate-check

Evaluate Renovate dependency update PRs and generate Japanese assessment reports.

Community
Advanced
whywaitawhywaita

build-validator

Automate post-change build validation across Node.js, Go, Python, and Rust projects.

Community
Intermediate
masermediagroup-stackmasermediagroup-stack
1

next-upgrade

Upgrade Next.js projects across major versions using official guides and codemods.

Community
Advanced
limerickgdslimerickgds
1

release-skills

Automate release management with version bumps, changelogs, commits, and Git tags.

Community
Advanced