agentleFS
acquiaacquia/acquia-skills-private/skills/playbooks/drupal-update-deploy/SKILL.md

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

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
  1. Distinctive:

    Ask the user: "Do you need to apply dependency updates first, or are updates already done?"

    line 28
  2. Distinctive:

    If updates are needed → follow Security Updates or Dependency Updates depending on the use case, then return here.

    line 30
  3. Distinctive:

    If updates are already applied → proceed to Step 2.

    line 31
  4. Distinctive:

    Always run these before asking the user where to deploy.

    line 37
  5. Distinctive:

    Before pushing, check for uncommitted changes:

    line 57
  6. Distinctive:

    If there are uncommitted changes, ask the user: "Do you want to commit these changes before deploying?"

    line 63
  7. Distinctive:

    If yes — ask for a commit message, then commit:

    line 65
  8. Distinctive:

    If no — warn the user that uncommitted changes will not be included in the deployment and confirm they want to proceed.

    line 70
  9. Distinctive:

    Follow Pull & Push for full options (selecting environments, handling conflicts).

    line 82
  10. Distinctive:

    After pushing, switch the environment to the updated branch using the environment ID from Step 2:

    line 88
  11. Distinctive:

    Follow Environment Management for deploy options.

    line 94
  12. Distinctive:

    Ask the user: "Do you want to trigger a pipeline build for the deployed branch?"

    line 100
  13. Distinctive:

    If yes → follow Pipeline Operations to start the build and stream logs:

    line 102
  14. Distinctive:

    If no → workflow complete.

    line 108
  15. Distinctive:

    After the pipeline completes (or if skipping pipelines), confirm the environment is running the expected code:

    line 114
  16. Very specific:

    Check the vcs field of the target environment to confirm the branch matches.

    line 120

≈ “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.

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

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:list

Output 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 status

If 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:code

Follow 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

StepToolSkill
Update packagescomposerdrupal-maintenance-security-updates or drupal-maintenance-dependency-updates
Fetch application + environmentsacliacli-application-management, acli-environment-management
Commit code changesgit—
Push codeacliacli-pull-push
Deploy to environmentacliacli-environment-management
Trigger pipelinepipelines-clipipelines-cli-pipeline-operations

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.