What problem does it solve?
Manually reviewing Renovate dependency-bump PRs is risky and time-consuming: changelogs are long, breaking changes hide in minor releases, and a green CI run does not prove the app still works. This Skill automates evidence-backed triage so you know whether a bump is safe to merge.
Core Features & Use Cases
- Automated PR triage: Picks the first open Renovate PR, parses the package/version table, and classifies each bump as patch, minor, major, or security.
- Changelog and source-diff analysis: Fetches GitHub releases, CHANGELOGs, and upstream compare diffs to surface breaking changes that affect APIs your codebase actually calls.
- Runtime verification: Checks out the PR branch (in place or in a worktree), starts the dev stack, and exercises affected code paths via PM2 logs, Maple traces, Chrome DevTools, and curl API checks.
- Use Case: Ask the agent to triage the latest Renovate PR bumping nodemailer; it greps your imports, triggers a password-reset email, verifies it lands in Mailpit, and returns a per-package verdict (SAFE / LIKELY SAFE / NEEDS CODE CHANGES / UNSAFE / CANNOT ASSESS).
Quick Start
Ask the agent to test the first open Renovate PR and report whether the dependency bump is safe to merge.