dependency-upgrade

To analyze Renovate pull requests for breaking changes, this Skill parses upstream release notes and changelogs to identify version bump types and assesses practical impact scope. It then generates a concise PR summary recommending whether the dependency upgrade is safe to approve, needs review, or should be escalated into a plan or epic.

Dependency upgrade impact assessment evaluates which files, modules, and tests are affected by modifying version catalogs or build files. This Skill performs this assessment by parsing Renovate-generated release notes and upstream changelogs to scope the practical impact of the update and identify potential breaking behavior.

You can automate dependency upgrade reviews using GitHub CLI and changelog analysis by having this Skill read Renovate-labeled open PRs. It optionally uses MCP-assisted code and documentation lookups to support posting concise PR summary comments directly to the repository with approval recommendations.

Dependency-upgrade works with Renovate-labeled open PRs that modify version catalogs, build files, or package manifests. It requires GitHub CLI access to parse release notes and applies breaking-change analysis, impact scoping, and handoff decisions to these dependency modification pull requests.

You should escalate a dependency upgrade into a plan or epic when the breaking-change analysis and impact assessment indicate high risk. This Skill provides decision support by recommending escalation for updates that require thorough review based on changelog parsing and affected module scoping.

The best way to review dependency bumps for breaking changes is to analyze upstream release pages and changelogs while checking affected files and tests. This Skill automates that process by reading Renovate-generated notes and producing a review summary with risk assessment and handoff decisions.