Dependabot PR Rollup
Developmentdependabot-pr-rollupDependabot PR Rollup is an Agent Skill for development published in the astral-sh/setup-uv repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Find open Dependabot PRs for the current GitHub repo, compare each PR head to its base branch, replay only the net dependency changes in a fresh worktree and branch, run npm validation, and optionally commit, push, and open a PR. Use when you want to batch or manually replicate active Dependabot updates.
QUICK START
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/astral-sh/setup-uv/blob/HEAD/.agents/skills/dependabot-pr-rollup/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/dependabot-pr-rollup, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Dependabot PR Rollup
When to use
Use this skill when the user wants to:
- find all open Dependabot PRs in the current repo
- reproduce their net effect in one local branch
- validate the result with the repo's standard npm checks
- optionally commit, push, and open a PR
Workflow
- Inspect the current checkout state, but do not reuse a dirty worktree.
- List open Dependabot PRs with
gh pr list --state open --author app/dependabot. - For each PR, collect the title, base branch, head branch, changed files, and relevant diffs.
- Compare each PR head against
origin/<base>instead of trusting the PR title. Dependabot PRs can already be partially merged, superseded by newer versions, or have no remaining net effect. - Create a new worktree and branch from
origin/<base>. - Reproduce only the remaining dependency changes in the new worktree.
- Inspect
package.jsonbefore editing. - Run
npm ci --ignore-scriptsbefore applying updates. - Use
npm install ... --ignore-scriptsfor direct dependency changes sopackage-lock.jsonstays in sync. - When updating
@biomejs/biome, also update the Biome schema URL version inbiome.jsonto match the installed Biome version.
- Inspect
- Run
npm run all. - If requested, commit the changed source, lockfile, and generated artifacts, then push and open a PR.
Repo-specific notes
- Use
ghfor GitHub operations. - Keep the user's original checkout untouched by working in a separate worktree.
- In this repo,
npm run allis the safest validation command because it runs build, check, package, and test. - If dependency changes affect bundled output, include the regenerated
dist/files.
Report back
Always report:
- open Dependabot PRs found
- which PRs required no net changes
- new branch name
- new worktree path
- files changed
npm run allresult- if applicable, commit SHA and PR URL