renovate-triage
Live data
- Open Renovate PRs authored by
app/renovate on your repos: !gh search prs --author app/renovate --state open --json repository,title,number,url --limit 100 2>/dev/null || echo "gh unavailable or not authenticated"
When to activate
- User says "renovate triage", "review dep PRs", "monthly deps", "batch deps".
- It's the 1st of the month and deps are grouped monthly.
Skip if: the user is asking about a single specific PR (use a PR-review skill instead), or if Renovate isn't configured on their repos.
Steps
- Use the live PR list above. Do not re-fetch.
- Group by repo. One repo's PRs often share the same grouping rule.
- For each PR, fetch merge state and CI:
gh api repos/{owner}/{repo}/pulls/{num} --jq '{mergeable, mergeStateStatus, title, labels}'gh pr checks <url>
- Classify each PR:
- Merge -- CI green, patch or minor bump, library is stable and well-adopted, no flags in the repo's Renovate config.
- Close -- superseded by a newer PR, wrong repo, duplicate, or abandoned.
- Defer -- major version bump, known breaking change, CI red that needs investigation, or a library that the repo pins deliberately.
- Output a table grouped by repo with recommended action per PR.
- Do not merge automatically. Present the plan; the user approves.
- After approval, merge in order, one repo at a time, verifying CI between merges (not in parallel).
Rules
- Never merge a Renovate PR with unresolved security findings on the PR or the repo.
@types/*-only bumps can silently break builds -- always check CI is green before merging, not just "mergeable".- Major bumps always defer. React 18 -> 19, Next 14 -> 15, Node 20 -> 22, etc. These are planned work, not routine hygiene.
- Close old superseded PRs before merging the latest one in a grouped series -- otherwise Renovate may reopen them.
Output
| Repo | PR | Bump | CI | Action | Notes |
|---|---|---|---|---|---|
Group by repo. After the table, list the proposed merge order across all repos.
1---2name: renovate-triage3description: Use when triaging open Renovate PRs across your own repos into merge / close / defer. Activates on "renovate triage", "review dep PRs", "monthly deps", or on the 1st of a month if deps are grouped monthly.4---56# renovate-triage78## Live data910- Open Renovate PRs authored by `app/renovate` on your repos: !`gh search prs --author app/renovate --state open --json repository,title,number,url --limit 100 2>/dev/null || echo "gh unavailable or not authenticated"`1112## When to activate1314- User says "renovate triage", "review dep PRs", "monthly deps", "batch deps".15- It's the 1st of the month and deps are grouped monthly.1617Skip if: the user is asking about a single specific PR (use a PR-review skill instead), or if Renovate isn't configured on their repos.1819## Steps20211. **Use the live PR list above.** Do not re-fetch.222. **Group by repo.** One repo's PRs often share the same grouping rule.233. **For each PR, fetch merge state and CI:**24 - `gh api repos/{owner}/{repo}/pulls/{num} --jq '{mergeable, mergeStateStatus, title, labels}'`25 - `gh pr checks <url>`264. **Classify each PR:**27 - **Merge** -- CI green, patch or minor bump, library is stable and well-adopted, no flags in the repo's Renovate config.28 - **Close** -- superseded by a newer PR, wrong repo, duplicate, or abandoned.29 - **Defer** -- major version bump, known breaking change, CI red that needs investigation, or a library that the repo pins deliberately.305. **Output a table** grouped by repo with recommended action per PR.316. **Do not merge automatically.** Present the plan; the user approves.327. **After approval,** merge in order, one repo at a time, verifying CI between merges (not in parallel).3334## Rules3536- **Never** merge a Renovate PR with unresolved security findings on the PR or the repo.37- `@types/*`-only bumps can silently break builds -- always check CI is green before merging, not just "mergeable".38- **Major bumps always defer.** React 18 -> 19, Next 14 -> 15, Node 20 -> 22, etc. These are planned work, not routine hygiene.39- Close old superseded PRs before merging the latest one in a grouped series -- otherwise Renovate may reopen them.4041## Output4243```text44| Repo | PR | Bump | CI | Action | Notes |45|---|---|---|---|---|---|46```4748Group by repo. After the table, list the proposed merge order across all repos.
Sagargupta16