Codestudio

Skill acquia/acquia-skills/skills/acli/codestudio

Install

npx -y skills add acquia/acquia-skills --skill codestudio

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

8 stars8 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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.

The file declares its own license as Proprietary. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

3.6 KB, as published. Nobody here has run it

Code Studio with Acquia CLI

Use when:

Setting up a new Code Studio project for a Cloud application
Changing the PHP version used in Code Studio builds
Migrating an existing acquia-pipelines.yml to a .gitlab-ci.yml file

Note: This skill covers Code Studio setup only. To trigger builds, check job status, or stream logs, use pipelines-cli (pipelines-cli-pipeline-operations).

Code Studio is Acquia's GitLab-based CI/CD platform. It runs build pipelines, automated tests, and deployments for your Cloud Platform applications.

Set Up Code Studio (Wizard)

The wizard creates and configures a Code Studio project for your application:

acli codestudio:wizard

Alias: acli cs:wizard

The wizard will:

Authenticate with your Cloud Platform application
Connect to your GitLab instance
Create or configure a Code Studio project
Set up CI/CD variables

Non-interactive (provide all credentials upfront):

acli codestudio:wizard \
  --key="$ACQUIA_KEY" \
  --secret="$ACQUIA_SECRET" \
  --gitlab-token="$GITLAB_TOKEN" \
  --gitlab-project-id=12345 \
  --gitlab-host-name=code.acquia.com

Security: Never pass credential values directly in the command line — they appear in shell history and process listings. Always source them from environment variables or a secrets manager.

Options:

Option	Description
`--key`	Cloud Platform API key for Code Studio to use
`--secret`	Cloud Platform API secret for Code Studio to use
`--gitlab-token`	GitLab personal access token
`--gitlab-project-id`	Integer project ID of the GitLab project to configure
`--gitlab-host-name`	GitLab hostname (defaults to Acquia's instance)

Change PHP Version in Code Studio

Update the PHP version used in Code Studio build containers:

acli codestudio:php-version <version>

Example:

acli codestudio:php-version 8.2
acli codestudio:php-version 8.3

Typical Workflow: Onboard to Code Studio

# Step 1: Set up Code Studio project
acli codestudio:wizard

# Step 2: Set PHP version if needed
acli codestudio:php-version 8.2

Best Practices

Run the wizard first — It sets up all required CI/CD variables automatically.
Use environment variables for credentials in CI — Pass --key, --secret, and --gitlab-token via environment variables (e.g., --key="$ACQUIA_KEY"), never as literal values. Store secrets in your CI/CD platform's secret store.
Match PHP versions — Ensure codestudio:php-version matches the version in your composer.json platform requirements.

Troubleshooting

"GitLab project not found"

Verify the project ID and that your token has access:

# Re-run wizard interactively to select the right project
acli codestudio:wizard

Authentication errors

Ensure your Cloud API key/secret are valid:

acli auth:login
acli auth:me