// Review Renovate dependency upgrade PRs to assess safety and effort. Use when reviewing PRs from Renovate bot that update NPM dependencies.
| name | renovate-review |
| description | Review Renovate dependency upgrade PRs to assess safety and effort. Use when reviewing PRs from Renovate bot that update NPM dependencies. |
| disable-model-invocation | false |
| argument-hint | [pr-number] [--comment] |
| allowed-tools | Bash, Grep, Glob, Read, WebFetch |
| scope | ["dependencies","review"] |
Review a Renovate PR to assess the safety and effort required to merge a dependency upgrade.
pr-number (required): The PR number to review--comment (optional): Post the assessment as a PR comment. If omitted, only output the review locally.gh pr view $ARGUMENTS --json title,body,files
Extract the following information:
We assume packages follow Semantic Versioning. Fix and minor should contain no breaking changes per semver
In all cases you must:
Research breaking changes by:
https://github.com/<owner>/<repo>/releasesIdentify which breaking changes may affect this codebase
Search for usage of the upgraded package:
Create a markdown comment with the following structure:
## Dependency Upgrade Review: `<package-name>`
<!-- For High risk only, add at the top: -->
> [!CAUTION]
> Breaking changes affect this codebase. Code changes required before merge.
<!-- For Medium risk only, add at the top: -->
> [!WARNING]
> Major upgrade with breaking changes. Review recommended.
`<old>` → `<new>` (**patch** / **minor** / **major**)
**Risk:** Low / Medium / High
**Impact:** <count> files
**Recommendation:** Safe to merge / Review recommended / Changes required
<one-line explanation>
<details>
<summary>Affected files</summary>
- `path/to/file.ts`
- ...
</details>
<!-- For major upgrades only: -->
<details>
<summary>Breaking changes</summary>
- <breaking change 1>
- <breaking change 2>
</details>
<details>
<summary>Required code changes</summary>
- <change 1>
- <change 2>
<!-- Or "None" if no changes needed -->
</details>
--comment flag provided)Only post the comment to the PR if the --comment flag was included in the arguments.
If --comment is provided:
gh pr comment <pr-number> --body "<assessment>"
If --comment is NOT provided, skip this step and only display the assessment locally.
Risk:
Impact:
Recommendation:
Set up the restore-context hook so skills can resume workflows after /clear and /compact. Use when setting up a new project or after cloning a repo that uses restore-context skills.
Manage restore context files so skills can survive /clear and /compact. Use to write, delete, check, or list .agent-restore-context-* files.
Fetch Jira ticket, create branch, implement changes, commit, push, open PR.
Generate AI-assisted navigation aids to help humans start reviewing a pull request more efficiently. Use when starting a PR review to get oriented on large or unfamiliar changes.
Persist guidelines, conventions, and architectural decisions into the repository's knowledge base. Use when told to remember something for future sessions.
Perform migrations for Renovate dependency upgrades based on breaking changes identified in a review. Use after running /renovate-review.