agentleFS
Sign inStart free
AstralKnown publisherastral-sh/setup-uv/.agents/skills/dependabot-pr-rollup/SKILL.md

dependabot-pr-rollup

Skill905 starsChanged 3 months agoMITView on GitHub

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.

  • Installs packages
  • Commits and pushes

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 1

    1. astral-sh/ruff-action★ 27660% same

    Wrote their own version · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repositoryOne other file it gives its agents.

The file

We split this skill into the rules it gives an agent

12 rules. About 0 are common, 4 are distinctive, and 8 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 8

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when the user wants to:

    line 12
  2. Very specific:

    commit and push the validated changes, then open a PR labeled dependencies

    line 16
  3. Very specific:

    Create a new worktree and branch from origin/<base>.

    line 24
  4. Very specific:

    Run npm ci --ignore-scripts before applying updates.

    line 27
  5. Very specific:

    Use npm install ... --ignore-scripts for direct dependency changes so package-lock.json stays in sync.

    line 28
  6. Very specific:

    When updating @biomejs/biome, also update the Biome schema URL version in biome.json to match the installed Biome version.

    line 29
  7. Distinctive:

    Commit the changed source, lockfile, and generated artifacts, then push the branch.

    line 31
  8. Very specific:

    Always open a pull request for the rollup and add the dependencies label to it.

    line 32
  9. Very specific:

    Use gh for GitHub operations.

    line 36
  10. Distinctive:

    Keep the user's original checkout untouched by working in a separate worktree.

    line 37
  11. Very specific:

    If dependency changes affect bundled output, include the regenerated dist/ files.

    line 39
  12. Distinctive:

    commit SHA and PR URL

    line 50

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free