renovate-prs

Triage, complete, and merge Renovate dependency PRs in a k3s homelab repository.

2|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/DanielH2018/server --skill renovate-prs-danielh2018
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: renovate-prs
Source: https://github.com/DanielH2018/server/tree/main/.claude/skills/renovate-prs
Command: npx skills add https://github.com/DanielH2018/server --skill renovate-prs-danielh2018

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Renovate opens pull requests that are deliberately incomplete — rules with automerge: false carry work orders in their group names, branches go stale against master, and some updates never become PRs at all. Merging these on green CI ships half-done dependency bumps, broken download URLs, or silent no-ops. ## Core Features & Use Cases - PR triage by class: Compare each PR's merge base against origin/master, read the file list and diff, and classify it (lock file, k8s image pin, host plane, tooling) to decide the handling path. - Finish incomplete bumps: Read the producing rule in renovate.json, verify rewritten download URLs and checksums against the publisher's manifest, and complete coupled pins (e.g., jellyfin server + plugin ABI) in a worktree on top of the bot's commit. - Orphan branch census: Detect renovate/* branches that no open PR or Dependency Dashboard entry speaks for, classify them as settled, dead, or lost updates, and report them without deleting. - Use Case: A green Renovate PR bumps a plugin version but leaves a 404 asset URL and a stale checksum — this Skill walks you through catching the mismatch, fixing the pin, and landing it through the serialized land.sh flow. ## Quick Start Ask the assistant to go through the open Renovate PRs, triage each one, finish any incomplete bumps, and land them one at a time.

Frequently Asked Questions about renovate-prs

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

FAQPage Schema
How do I triage open Renovate pull requests on GitHub?▼

List PRs with `gh pr list --author app/renovate`, then compare each PR's baseRefOid against origin/master before reading the diff. Classify by the files touched — lock files merge directly, image pins need deployment, and titles with a `manual —` parenthetical name unfinished work.

Why does a green Renovate PR still break after merging?▼

Renovate's regex managers rewrite only what their matchStrings capture, so a version appearing twice in a URL or coupled to a checksum can be half-updated while CI stays green. Verify the new URL returns HTTP 200 and its content matches the pinned checksum before merging.

How do I find what a Renovate packageRule requires manually?▼

Query renovate.json with jq: select packageRules whose groupName matches the PR title fragment and read the description field. Every automerge:false rule in this repo explains why it cannot automerge, which is exactly the work left to finish.

Can Renovate updates exist without an open pull request?▼

Yes. Updates can sit in the Dependency Dashboard's Pending Status Checks section past their minimumReleaseAge without a PR. Ticking the item's checkbox on the dashboard issue forces Renovate to create the branch and PR within minutes.

Should I delete stale renovate branches after merging?▼

No — report orphan branches, never delete them unilaterally. A branch with no PR is not proof the work is gone; classify each as settled, targeting a removed dependency, or a lost pending update, and let the operator decide on any sweep.