bundle-dependency-prs
Skill23 starsChanged 4 months agoMITView on GitHub
Fix broken dependency update PRs and aggregate the ones that work into one PR.
8 other projects use a version of this.
Adopted by
Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data
Most recently taken up by
- microsoft/VSSDK-Analyzersword for word, first seen Nov 8, 2026
- microsoft/json-document-transformsword for word, first seen Oct 13, 2026
- microsoft/slow-cheetahword for word, first seen Oct 13, 2026
- microsoft/vs-servicehubword for word, first seen Jul 15, 2026
- microsoft/vs-mefword for word, first seen Jul 13, 2026
- microsoft/vs-streamjsonrpcword for word, first seen Jul 13, 2026
Other versions8 projects use a version of this.
Word for word · 8
- microsoft/vs-threading★ 1k100% same
- microsoft/vs-streamjsonrpc★ 943100% same
- microsoft/vs-mef★ 469100% same
- microsoft/slow-cheetah★ 353100% same
- microsoft/vs-validation★ 144100% same
- microsoft/json-document-transforms★ 117100% same
- microsoft/VSSDK-Analyzers★ 56100% same
- microsoft/vs-servicehub★ 31100% same
Edited · 0
None found.
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 repository3 other files it gives its agents.
- AGENTS.mdAGENTS.md
- testingSkill
- update-library-templateSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 8 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
Always validate your changes locally before pushing them to the remote repository.
- Distinctive: line 19
When writing PR bodies or comments, avoid unmatched markdown code fences.
- Distinctive: line 22
If a docfx check fails but all other checks succeed, then that is a 'successful' dependency update PR.
- Distinctive: line 26
Before aggregating PRs, first try to fix any individual dependency update PRs with failing build/test checks.
- Very specific: line 30
If pushing to a repo in the microsoft org when the PR is authored by renovate, follow-up the push with a PR comment that says exactly this: …
- Distinctive: line 31
If you can't fix a particular PR, add a comment to the PR describing your attempt and outcome.
- Distinctive: line 38
Consider that a remote branch by the same name may already exist.
- Distinctive: line 42
Consider that your local branch may have already merged an equivalent PR in the past (from a past run).
- Distinctive: line 46
Create a PR, if one does not already exist.
≈ “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.
Files
Instructions
You have two goals:
- Get all dependency PRs to a state where their PR checks pass.
- Aggregate dependency PRs with passing checks into just one PR.
You can identify dependency update PRs by those authored by dependabot or renovate.
You'll find instructions for building and validating the repo in the CONTRIBUTING.md doc. Always validate your changes locally before pushing them to the remote repository.
When writing PR bodies or comments, avoid unmatched markdown code fences. Keep markdown well-formed.
For purposes of assessing PR readiness by its PR checks, consider docfx related checks to be irrelevant. If a docfx check fails but all other checks succeed, then that is a 'successful' dependency update PR.
Fix up dependency PRs with failing checks
Before aggregating PRs, first try to fix any individual dependency update PRs with failing build/test checks.
- For the dependency PRs with failing build or test PR checks, check out their source branch and fix any issues.
- Push your fixes as fresh commits to the individual dependency PRs.
If pushing to a repo in the
microsoftorg when the PR is authored byrenovate, follow-up the push with a PR comment that says exactly this: "/azp run" which triggers PR checks to re-run. - If you can't fix a particular PR, add a comment to the PR describing your attempt and outcome.
Group dependency PRs that are ready to go
Your next goal is to collect all the dependency updates that are ready to go into a single PR.
- Prepare a local branch called
bulkDepUpdates.- Consider that a remote branch by the same name may already exist. If it does, base your local branch on it.
- Merge
origin/maininto this branch. - Resolve any conflicts.
- For the dependency PRs whose build and test PR checks already pass, merge them into the
bulkDepUpdatesbranch. Consider that your local branch may have already merged an equivalent PR in the past (from a past run). If so, you should skip merging that PR. Resolve any conflicts. Build and run tests to validate your branch. - Push the branch.
- Create a PR, if one does not already exist.
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
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.