acquia-skills

Use when user asks about updating outdated Drupal packages, upgrading Drupal core minor or patch versions, updating contrib modules, or resolving composer version conflicts.

Use when user asks about fixing security vulnerabilities, composer audit failures, vulnerable Drupal packages, or CVE advisories in a Drupal codebase.

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.

Use when listing Acquia Cloud applications, linking or unlinking a local repo to an application, opening an app in browser, checking VCS/branch deployment status, or exporting a site archive.

Use when setting up a new Code Studio (GitLab CI/CD) project, changing PHP version in Code Studio builds. NOT for checking pipeline job status — use pipelines-cli-pipeline-operations for that.

Use when listing, creating, deleting, or mirroring Cloud environments, managing CDEs, deploying code to an environment, or checking environment status.

Use when acli is not installed, authentication fails, or user needs to install and authenticate acli for the first time.

Use when creating, listing, opening, deleting, or managing Cloud IDEs, or checking IDE hibernation status, changing PHP version in IDE, or sharing an IDE with teammates.

Use when syncing code, database, or files between local and Acquia Cloud environments, or pulling a Cloud database/files locally.

Use when SSHing into a Cloud environment, running Drush commands remotely, or tailing live application logs.

Use when running acli commands non-interactively in scripts, CI/CD pipelines, or automation where interactive prompts must be suppressed.

Use when adding, listing, or deleting SSH keys for Acquia Cloud access, or when SSH access is denied due to missing keys.

Use when acli commands fail, return unexpected errors, authentication breaks, or the CLI behaves unexpectedly.

Use when finding a pipelines application ID or linking a repo before running any pipelines-cli command that needs --application-id.

Use when pipelines CLI is not installed, authentication fails, or user needs to set up pipelines-cli for the first time.

Use when user asks about pipeline status, CI build status, triggering a build, streaming pipeline logs, terminating a job, or checking if a pipeline passed or failed. Use pipelines-cli, NOT acli.