renovate-pr

Tests and assesses open Renovate dependency-bump pull requests for merge safety.

6.1k|768|Updated Mar 19, 2021
One-click install
npx skills add https://github.com/lightdash/lightdash --skill renovate-pr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: renovate-pr
Source: https://github.com/lightdash/lightdash/tree/main/.claude/skills/renovate-pr
Command: npx skills add https://github.com/lightdash/lightdash --skill renovate-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about renovate-pr

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

FAQPage Schema
How do I test a Renovate dependency bump PR before merging?

Check out the Renovate PR branch, read the changelog for breaking changes, grep your codebase for direct imports of the upgraded package, then run the app and exercise the affected flows. This Skill automates that full sequence and returns an evidence-backed verdict.

How to check if a dependency upgrade has breaking changes?

Fetch the upstream GitHub releases or CHANGELOG spanning old to new version and look for BREAKING entries, removed APIs, and new required configuration. If the changelog is vague on a major bump, compare the upstream source diff for the specific APIs your code calls.

Does this work with pnpm monorepos and multiple packages in one PR?

Yes. It parses every package in the Renovate PR table, greps usage across packages/* directories, and scores each dependency independently before rolling up an overall verdict. Stale pnpm-lock.yaml is handled by regenerating and committing it.

What counts as a failure when testing a dependency upgrade?

Failure signals include stack traces in PM2 logs, new runtime errors in Maple traces, HTTP 500s on previously working endpoints, browser console errors not present on main, and visible behavior changes. Pre-existing unrelated errors and harmless deprecation warnings do not count.

Can this skill merge or approve the Renovate PR automatically?

No. The skill only triages and reports a recommendation such as merge, merge with quick review, fix code first, or do not merge. It never approves, merges, or comments on the PR unless you explicitly ask.