drupal-update-deploy
Skill1 starsChanged 7 months agoMITView on GitHub
Use when user wants to update Drupal dependencies and deploy the changes to an Acquia environment, optionally triggering a pipeline build. Chains drupal-maintenance, acli, and pipelines-cli skills.
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- acquia/acquia-skillsedited, first seen Oct 9, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- acquia/acquia-skills★ 1080% 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 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
- dependency-updatesSkill
- security-updatesSkill
- application-managementSkill
- getting-startedSkill
- pipeline-operationsSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
16 rules. About 0 are common, 15 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈15
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 28
Ask the user: "Do you need to apply dependency updates first, or are updates already done?"
- Distinctive: line 30
If updates are needed → follow Security Updates or Dependency Updates depending on the use case, then return here.
- Distinctive: line 31
If updates are already applied → proceed to Step 2.
- Distinctive: line 37
Always run these before asking the user where to deploy.
- Distinctive: line 57
Before pushing, check for uncommitted changes:
- Distinctive: line 63
If there are uncommitted changes, ask the user: "Do you want to commit these changes before deploying?"
- Distinctive: line 65
If yes — ask for a commit message, then commit:
- Distinctive: line 70
If no — warn the user that uncommitted changes will not be included in the deployment and confirm they want to proceed.
- Distinctive: line 82
Follow Pull & Push for full options (selecting environments, handling conflicts).
- Distinctive: line 88
After pushing, switch the environment to the updated branch using the environment ID from Step 2:
- Distinctive: line 94
Follow Environment Management for deploy options.
- Distinctive: line 100
Ask the user: "Do you want to trigger a pipeline build for the deployed branch?"
- Distinctive: line 102
If yes → follow Pipeline Operations to start the build and stream logs:
- Distinctive: line 108
If no → workflow complete.
- Distinctive: line 114
After the pipeline completes (or if skipping pipelines), confirm the environment is running the expected code:
- Very specific: line 120
Check the vcs field of the target environment to confirm the branch matches.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
Drupal Update and Deploy Workflow
Use when:
- Applying Drupal dependency updates and deploying to an Acquia environment
- Running the full cycle: update packages → push code → deploy → trigger pipeline
Prerequisites: The following skill sets must be loaded:
drupal-maintenance,acli,pipelines-cli.
Workflow
Step 1 — Apply dependency updates
Ask the user: "Do you need to apply dependency updates first, or are updates already done?"
- If updates are needed → follow Security Updates or Dependency Updates depending on the use case, then return here.
- If updates are already applied → proceed to Step 2.
Step 2 — Fetch application and environments
Always run these before asking the user where to deploy. This ensures the correct application and environment IDs are used.
# List available applications and note the UUID
acli api:applications:listOutput shows application names and UUIDs. Ask the user: "Which application do you want to deploy to?" and confirm the UUID.
# List environments for the selected application
acli api:environments:list <app-uuid>Output shows environment labels (dev, stage, prod, CDEs), IDs, and the currently deployed branch. Ask the user: "Which environment do you want to deploy to?"
Step 3 — Commit code changes
Before pushing, check for uncommitted changes:
git statusIf there are uncommitted changes, ask the user: "Do you want to commit these changes before deploying?"
- If yes — ask for a commit message, then commit:
git add -A git commit -m "<user-provided message>" - If no — warn the user that uncommitted changes will not be included in the deployment and confirm they want to proceed.
Step 4 — Push code to Acquia Cloud
Push the committed code to the selected environment:
acli push:codeFollow Pull & Push for full options (selecting environments, handling conflicts).
Step 5 — Switch code on the environment
After pushing, switch the environment to the updated branch using the environment ID from Step 2:
acli api:environments:switchCode <environment-id> --branch=<branch-name>Follow Environment Management for deploy options.
Step 6 — Trigger a pipeline build (optional)
Ask the user: "Do you want to trigger a pipeline build for the deployed branch?"
- If yes → follow Pipeline Operations to start the build and stream logs:
pipelines start --application-id=<app-id> --vcs-path=<branch> --tail- If no → workflow complete.
Step 7 — Verify deployment
After the pipeline completes (or if skipping pipelines), confirm the environment is running the expected code:
acli api:environments:list <app-uuid>Check the vcs field of the target environment to confirm the branch matches.
Quick Reference
| Step | Tool | Skill |
| Update packages | composer | drupal-maintenance-security-updates or drupal-maintenance-dependency-updates |
| Fetch application + environments | acli | acli-application-management, acli-environment-management |
| Commit code changes | git | — |
| Push code | acli | acli-pull-push |
| Deploy to environment | acli | acli-environment-management |
| Trigger pipeline | pipelines-cli | pipelines-cli-pipeline-operations |
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.

