What problem does it solve? Renovate dependency-update PRs often sit open with failing CI, and it is unclear whether the failure is caused by your code, a pending approval, or a transient issue. This Skill triages the failure, decides whether the upgrade should happen at all, applies the follow-up fixes, and documents the reasoning on the PR without ever merging or approving it. ## Core Features & Use Cases - Upgrade feasibility research: Checks release announcements, peer dependency ranges via npm view, and upstream issue trackers before writing any migration code, so effort is not wasted on dependencies that should be skipped. - CI failure triage: Classifies failures into code-caused, approval/permission-pending, or transient, and reproduces them locally in a git worktree with the base branch merged in. - Follow-up fixes and lockfile handling: Commits migration fixes onto the Renovate branch itself, regenerates lockfiles instead of hand-editing them, and verifies the build actually runs (HTTP 200, CLI invocation) rather than trusting green tests. - Use Case: A Renovate PR bumps a major version of a build tool and CI fails. The Skill investigates whether the ecosystem supports the new version, reproduces the failure locally, fixes the breaking API usage, benchmarks before/after if speed was the selling point, and posts a comment on the PR summarizing findings. ## Quick Start Ask the assistant to resolve the open Renovate PR for a given repository, optionally passing a PR number or URL such as "resolve Renovate PR #142".
