setup-uv/.agents/skills/dependabot-pr-rollup/SKILL.md

name, description, license, compatibility

name	description	license	compatibility
dependabot-pr-rollup	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, then commit, push, and open a pull request labeled dependencies. Use when you want to batch or manually replicate active Dependabot updates.	MIT	Requires git, git worktree, gh CLI auth, npm, and a GitHub repo with an origin remote.

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
• commit and push the validated changes, then open a PR labeled dependencies

Workflow

1. Inspect the current checkout state, but do not reuse a dirty worktree.
2. List open Dependabot PRs with gh pr list --state open --author app/dependabot.
3. For each PR, collect the title, base branch, head branch, changed files, and relevant diffs.
4. 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.
5. Create a new worktree and branch from origin/<base>.
6. Reproduce only the remaining dependency changes in the new worktree.
   • Inspect package.json before editing.
   • Run npm ci --ignore-scripts before applying updates.
   • Use npm install ... --ignore-scripts for direct dependency changes so package-lock.json stays in sync.
   • When updating @biomejs/biome, also update the Biome schema URL version in biome.json to match the installed Biome version.
7. Run npm run all.
8. Commit the changed source, lockfile, and generated artifacts, then push the branch.
9. Always open a pull request for the rollup and add the dependencies label to it. Pass --label dependencies to gh pr create, or add the label immediately afterward with gh pr edit --add-label dependencies.

Repo-specific notes

• Use gh for GitHub operations.
• Keep the user's original checkout untouched by working in a separate worktree.
• In this repo, npm run all is 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 all result
• commit SHA and PR URL
• confirmation that the PR has the dependencies label