agentleFS
acquiaacquia/acquia-skills-private/skills/acli/codestudio/SKILL.md

codestudio

Skill1 starsChanged 7 months agoMITView on GitHub

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.

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create or configure a Code Studio project

    line 40
  2. Distinctive:

    Update the PHP version used in Code Studio build containers:

    line 70
  3. Distinctive:

    Verify the project ID and that your token has access:

    line 108
  4. Distinctive:

    Ensure your Cloud API key/secret are valid:

    line 117

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

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:

  1. Authenticate with your Cloud Platform application
  2. Connect to your GitLab instance
  3. Create or configure a Code Studio project
  4. 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:

OptionDescription
--keyCloud Platform API key for Code Studio to use
--secretCloud Platform API secret for Code Studio to use
--gitlab-tokenGitLab personal access token
--gitlab-project-idInteger project ID of the GitLab project to configure
--gitlab-host-nameGitLab 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

  1. Run the wizard first — It sets up all required CI/CD variables automatically.
  2. 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.
  3. 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

Related Topics

  • Getting Started — Authentication setup
  • Environment Management — Deploy to environments
  • Pull & Push — Push build artifacts

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.