Skip to content
Skills Library
DevOps & cloud · Testing

testbox

/testbox

Run CI commands against local changes in a real Semaphore environment. Use when the user wants to test code before pushing, run tests in CI env, or iterate fast on fixes — e.g. "run tests", "test before pushing", "try this in CI", "does this pass", "test my changes", "run the build", "check if tests pass", "spin up CI environment".

Repository
sem-ai ↗
Licence
Apache-2.0
Last repository change
06.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 06.10.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Run CI commands against local changes in a real Semaphore environment. Use when the user wants to test code before pushing, run tests in CI env, or iterate fast on fixes — e.g. "run tests", "test before pushing", "try this in CI", "does this pass", "test my changes", "run the build", "check if tests pass", "spin up CI environment".

Triggers from the description

run teststest before pushingtry this in CIdoes this passtest my changesrun the buildcheck if tests passspin up CI environment
Original author description

Run CI commands against local changes in a real Semaphore environment. Use when the user wants to test code before pushing, run tests in CI env, or iterate fast on fixes — e.g. "run tests", "test before pushing", "try this in CI", "does this pass", "test my changes", "run the build", "check if tests pass", "spin up CI environment".

How it works

  1. Workflow
  2. Best practices for agents
  3. Typical agent loop
Original SKILL.md headings · 76 lines, 376 words
SKILL.md preview
---
name: testbox
description: Run CI commands against local changes in a real Semaphore environment. Use when the user wants to test code before pushing, run tests in CI env, or iterate fast on fixes — e.g. "run tests", "test before pushing", "try this in CI", "does this pass", "test my changes", "run the build", "check if tests pass", "spin up CI environment".
user-invocable: false
---

# Testbox — Run CI locally in a real Semaphore environment

Testbox creates a Semaphore CI job you can run commands against via SSH. Same machine type, OS image, secrets, and cache as your real pipelines. Zero new infrastructure.

## Workflow

### 1. Warm up (once per session)

```bash
sem-ai testbox warmup --project my-app
```

Returns a testbox ID + SSH info. The VM is ready when the command returns.

Options:
```bash
--machine f1-standard-4       # bigger machine (default: f1-standard-2)
--os-image ubuntu2404          # different OS (default: ubuntu2204)
--duration 45m                 # longer session (default: 30m)
--idle-timeout 10m             # stop if no commands for N minutes (default: 30m)
```

### 2. Run commands (fast — rsync + SSH)

```bash
sem-ai testbox run --id <testbox-id> "go test ./..."
sem-ai testbox run --id <testbox-id> "make build"
sem-ai testbox run --id <testbox-id> "npm test"
```

Each `run` syncs only changed files (rsync checksum), then executes. After first sync, subsequent runs take 1-3 seconds for the sync.

### 3. Interactive SSH (optional)

```bash
sem-ai testbox ssh --id <testbox-id>
```

### 4. Stop when done

```bash
sem-ai testbox stop --id <testbox-id>
```

Or let it auto-expire after the duration/idle timeout.

## Best practices for agents

1. **Warm up immediately** when starting a coding task that involves CI. Don't wait until tests need to run.
2. **Reuse the testbox ID** across multiple `run` commands. Don't create a new testbox per test run.
3. **Route tests through testbox**, not locally. The CI environment has the correct dependencies, services, and secrets.
4. **After tests pass in testbox**, push the code. CI will confirm via the real pipeline.
5. **Stop the testbox** when the task is complete to avoid unnecessary billing.

## Typical agent loop

```bash
# Start of task
TESTBOX=$(sem-ai testbox warmup | jq -r '.testbox_id')   # --project auto-detected from origin (pass it only to override)

# Iterate on code
# ... make changes ...
sem-ai testbox run --id $TESTBOX "go test ./..."
# ... fix failures ...
sem-ai testbox run --id $TESTBOX "go test ./..."
# tests pass!

# After tests pass, push and verify in real CI — load the watch-after-push skill
# (it finds the run for your exact commit_sha and watches it).
git push

# Clean up
sem-ai testbox stop --id $TESTBOX
```

Versions

The database has no other skills named testbox.

Database snapshot: 13.11.2026 · package version b4b61a07efc4 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100local-ci
    Run GitHub Actions CI locally with Local CI to validate changes before pushing. Use when testing, running checks, or validating code changes.
  • 100watch-after-push
    After pushing commits to a Semaphore-backed repo, find the triggered CI run and watch it to completion, then report pass/fail. Use right after `git push`, or when the user asks "did my push pass", "watch CI", "is the build green", "what happened after I pushed", "watch the pipeline".
  • 100semaphore-ci
    Manage Semaphore CI/CD via sem-ai. Use when the user asks about CI status, pipeline failures, test results, deployments, secrets, notifications, scheduled tasks, deployment targets, project health, or anything related to their Semaphore pipelines and workflows — e.g. "CI…
  • 100semaphore-webhooks
    Receive and verify Semaphore CI webhooks (semaphore.io notifications). Use when setting up a Semaphore CI webhook endpoint, verifying the X-Semaphore-Signature-256 HMAC-SHA256 header, debugging 401 signature failures, or handling pipeline-finished notifications by…
  • 100semaphore
    Use when the person asks to message, reply to, or check messages from other people's agents or their own other agents, mentions Semaphore, their Semaphore inbox, contacts or channels, or asks which Semaphore agent to use here.
  • 100semaphore
    Use when the person asks to message, reply to, or check messages from other people's agents or their own other agents, mentions Semaphore, their Semaphore inbox, contacts or channels, or asks which Semaphore agent to use here.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.