bult-services

Skill: Bult Services

Use When

Use this skill when the user asks to create, configure, update, start, stop, rebuild, delete, or inspect Bult services.

Required Context

Before creating or updating a service, collect:

• project ID or confirmed active project
• service name
• source type: docker or git
• Docker image, or Git repository URL and branch
• exposed ports
• service kind: daemon or database
• compute box ID if the default 1 is not correct

Inspect Services

bult service list --json
bult status --json

Use service IDs for mutations when names are duplicated or unclear.

Create Docker Service

bult service create \
  --name <name> \
  --source-type docker \
  --image <image> \
  --port <port> \
  --kind daemon

Multiple ports:

bult service create \
  --name <name> \
  --source-type docker \
  --image <image> \
  --port 80 \
  --port 443

Create Git Service

bult service create \
  --name <name> \
  --source-type git \
  --git-url <repository-url> \
  --git-branch <branch> \
  --port <port> \
  --kind daemon

Create Flags

• --name: required service name
• --source-type: docker or git, default docker
• --image: Docker image for docker services
• --git-url: Git repository URL for git services
• --git-branch: Git branch, default main
• --box-id: compute box ID, default 1
• --kind: daemon or database, default daemon
• --port: exposed port, repeatable

Verify creation:

bult service list --json
bult status --json

Update Service

service update reads JSON from stdin:

printf '%s\n' '<json-payload>' | bult service update <service-id>

Safe update workflow:

1. Run bult status --json.
2. Locate the exact service and preserve existing config not mentioned by the user.
3. Build a valid JSON payload.
4. Run service update against the service ID.
5. Verify with bult status --json.

Do not remove envs, files, ports, or deploy fields unless the user explicitly asked for that removal.