Skip to content
arula

Take a change an AI wrote, check what could be wrong, and explain what you would approve, send back, or ask an owner to decide.

Start here / Installation

Install Workbench.
Check the workspace.

Get the commands, agent skills, and payments fixture ready before investigating the change.

Ready when

The installer’s checks pass, /workbench-health reports Status: healthy, the Round 0 diff is available, and speed help runs from the fixture.

Already installed? Run the checks below, then continue to the payments change.

1. Read the platform guide

Use Terminal. Apple Command Line Tools, Bash 4.3+, Node.js 22.18+, jq 1.7+, GNU coreutils, uv, tree-sitter CLI, and Claude Code installed and signed in. The script prepares Python 3.12+.

Open the macOS setup guide ↗

Upgrading a previous Workbench installation?

If workbench@mastercard-workbench is already installed, the platform guide instructs you to disable that user-scoped plugin before this setup. Follow its “Before You Begin” section.

2. Clone the installer

git clone https://github.com/ArulaAI/Workbench_Installer.git
cd Workbench_Installer

3. Run setup

bash mac/Workbench-Lab-Setup-Mac.sh

The script installs Workbench on feat/301-latest and prepares payments-validation-fixture on round-0. The default folder is ~/Lab.

Wait for:

Workbench is ready.

If setup stops, follow the instruction it displays and rerun the same script. It reuses completed setup steps.

4. Check from a new terminal

Open a new Terminal window and start Claude Code from the fixture:

cd ~/Lab/payments-validation-fixture
claude

Inside Claude Code, run /workbench-health. Expected result:

Status: healthy
Workbench skills were imported successfully and are ready to use.

Exit Claude Code. From the same fixture folder, check the change and the CLI:

git --no-pager diff --stat main...round-0
speed help

The diff command should list changed files. SPEED should show its available commands without errors. The guides confirm that commands installed as workbench also run as speed.

If a readiness check fails

If the command is not found, open a new Terminal window. If the health skill is missing, run workbench skills sync from the fixture, restart Claude Code, and retry. Use the platform guide’s troubleshooting section for other failures.

1. Read the platform guide

Use Git Bash. Git for Windows with Git Bash, Python 3.12+ with “Add python.exe to PATH” selected, Node.js 22.18+, and Claude Code installed and signed in. The script installs jq 1.7.1.

Open the Windows setup guide ↗

Upgrading a previous Workbench installation?

If workbench@mastercard-workbench is already installed, the platform guide instructs you to disable that user-scoped plugin before this setup. Follow its “Before You Begin” section.

2. Clone the installer

git clone https://github.com/ArulaAI/Workbench_Installer.git
cd Workbench_Installer

3. Run setup

bash windows/setup-windows.sh

The script installs Workbench on feat/301-latest and prepares payments-validation-fixture on round-0. The default folder is ~/lab.

Wait for:

Setup complete: all required tools and repositories are ready.

If setup stops, follow the instruction it displays and rerun the same script. It reuses completed setup steps.

4. Check from a new terminal

Open a new Git Bash window and start Claude Code from the fixture:

cd ~/lab/payments-validation-fixture
claude

Inside Claude Code, run /workbench-health. Expected result:

Status: healthy
Workbench skills were imported successfully and are ready to use.

Exit Claude Code. From the same fixture folder, check the change and the CLI:

git --no-pager diff --stat main...round-0
speed help

The diff command should list changed files. SPEED should show its available commands without errors. The guides confirm that commands installed as workbench also run as speed.

If a readiness check fails

If the command is not found, open a new Git Bash window. If the health skill is missing, run workbench skills sync from the fixture, restart Claude Code, and retry. Use the platform guide’s troubleshooting section for other failures.

In this class, paths labelled Fixture are relative to payments-validation-fixture; SPEED paths are relative to the installed workbench checkout. The original lesson names its teaching copy 301-config.

Use the reader’s archived source and recorded results alongside your checkout. Fresh agent output can differ from the saved walkthrough.

Continue to the payments change →

Instructions checked against Workbench Installer · 100386e. Current installer repository ↗