dependency-updates
Skill1 starsChanged 7 months agoMITView on GitHub
Use when user asks about updating outdated Drupal packages, upgrading Drupal core minor or patch versions, updating contrib modules, or resolving composer version conflicts.
7 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- naomiaro/waveform-playlisttheir own version, first seen Nov 16, 2026
- eclipse-enclave/enclavetheir own version, first seen Nov 1, 2026
- microsoft/lagetheir own version, first seen Nov 1, 2026
- ImranR98/Obtainiumtheir own version, first seen Oct 17, 2026
- acquia/acquia-skillsedited, first seen Oct 9, 2026
- championswimmer/TwoFactheir own version, first seen Oct 9, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- acquia/acquia-skills★ 1090% same
Wrote their own version · 6
- ImranR98/Obtainium★ 21ksame name
- naomiaro/waveform-playlist★ 1.7ksame name
- microsoft/lage★ 817same name
- championswimmer/TwoFac★ 130same name
- eclipse-enclave/enclave★ 80same name
- linchpin/skills★ 1same name
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 repository15 other files it gives its agents.
- application-managementSkill
- codestudioSkill
- environment-managementSkill
- getting-startedSkill
- ide-managementSkill
- pull-pushSkill
- remote-accessSkill
- scriptingSkill
- ssh-key-managementSkill
- troubleshootingSkill
- security-updatesSkill
- application-managementSkill
- getting-startedSkill
- pipeline-operationsSkill
- drupal-update-deploySkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 4 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 29
Check the current branch first:
- Distinctive: line 35
If the user is on main, master, or any protected branch, stop and ask: "What would you like to name the new branch for these updates?"
- Distinctive: line 49
Only continue to the next step once the output confirms a non-protected branch.
- Very specific: line 115
Update everything within existing composer.json constraints:
- Distinctive: line 157
Update both together to let composer find a compatible set:
- Very specific: line 165
If composer update introduced a regression, restore the previous lock file from version control and reinstall:
- Very specific: line 182
Run composer audit after any update to confirm no new advisories were introduced:
“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Dependency Updates for Drupal with Composer
Use when:
- Checking which packages are outdated
- Updating Drupal core to a newer minor or patch release
- Updating contrib modules or libraries
- Resolving composer version conflicts after an update
Before You Start — Create a Branch
This step is mandatory. Do not run any composer commands until a new branch is created and confirmed. Never update packages directly on
mainormaster.
Check the current branch first:
git branch --show-currentIf the user is on main, master, or any protected branch, stop and ask: "What would you like to name the new branch for these updates?"
Suggest a default if they are unsure (e.g., deps/drupal-updates-YYYY-MM-DD).
git checkout -b <branch-name>Confirm the new branch is active before proceeding:
git branch --show-currentOnly continue to the next step once the output confirms a non-protected branch.
Check for Outdated Packages
composer outdatedShows all packages with newer versions available. Columns: current version → latest available.
Check only direct dependencies
composer outdated --directCheck a specific package
composer outdated drupal/core-recommendedUpdate a Specific Package
composer update drupal/package --with-all-dependenciesUpdate multiple packages at once
composer update drupal/package1 drupal/package2 --with-all-dependenciesUpdate Drupal Core (Minor or Patch)
Drupal core is split across multiple packages. Update all together:
composer update drupal/core-recommended drupal/core-composer-scaffold drupal/core-project-message --with-all-dependenciesNote: Minor upgrades (e.g., 10.2 → 10.3) may require relaxing the version constraint in
composer.jsonfirst:"drupal/core-recommended": "^10.3"Then run the update command above.
Verify the installed version
composer show drupal/core | grep versionsUpdate All Packages
Update everything within existing composer.json constraints:
composer updateThis updates
composer.lockbut will not change version constraints incomposer.json. Packages pinned to an older major will not cross that boundary.
Update All Drupal Contrib Modules
composer update "drupal/*" --with-all-dependenciesResolving Conflicts
"Your requirements could not be resolved"
Find what is blocking the update:
# What requires the package you're trying to update?
composer why drupal/package
# What prevents the target version?
composer why-not drupal/package 2.xAdjust the conflicting constraint in composer.json and retry.
Conflict between two contrib modules
# Check full dependency chain
composer depends drupal/module-a
composer depends drupal/module-bUpdate both together to let composer find a compatible set:
composer update drupal/module-a drupal/module-b --with-all-dependenciesRevert a bad update
If composer update introduced a regression, restore the previous lock file from version control and reinstall:
git checkout composer.lock
composer installVerify the Update
# Confirm installed versions
composer show drupal/core-recommended
composer show --outdatedRun composer audit after any update to confirm no new advisories were introduced:
composer auditAfter verification, always ask the user these questions in order:
1. "Do you want to commit these changes?"
- If yes:
git add composer.json composer.lock git commit -m "Update Drupal dependencies"- If no → remind the user that
composer.jsonandcomposer.lockare uncommitted before proceeding.2. "Do you want to deploy these changes to an Acquia environment?"
- If yes → follow the Drupal Update and Deploy playbook to push code, switch the environment, and optionally trigger a pipeline build.
- If no → done.
Troubleshooting
| Problem | Command |
| Update ignored — package still old | Check constraint in composer.json; relax if needed |
composer install fails after update | Run composer why-not package version to find conflict |
| Unexpected packages changed | Review git diff composer.lock before committing |
| Memory limit error | COMPOSER_MEMORY_LIMIT=-1 composer update |
Related
- Security Updates — Fix specific vulnerability advisories
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.

