菜单
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".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Deploy via Semaphore promotions. Manage deployment targets, promote pipelines, deploy-and-wait.
Manage Semaphore infrastructure — secrets, notifications, agent types, scheduled tasks, artifacts.
Diagnose sem-ai plugin issues when the sem-ai binary isn't installed yet, and guide the user through binary install. Use when the user reports sem-ai not working, MCP tools missing, slash command not found, `sem-ai connect` failing, or sees "command not found: sem-ai".
Triage and FIX flaky tests on a Semaphore project end-to-end — find the worst offenders, pull history, locate the test in the code, diagnose the root cause, write a fix or justified quarantine, and verify by re-running. Use whenever the user wants to fix/investigate flaky tests, de-flake CI, reduce intermittent failures, asks "why is CI randomly red", wants to quarantine a flake, or after `sem-ai flaky list` surfaces offenders. Goes BEYOND detection (test-intelligence) to root-cause + code change + verification.
Diagnose and fix CI pipeline failures. Step-by-step debugging with sem-ai.
Translate a repo's GitHub Actions workflows into an equivalent Semaphore pipeline. ONLY covers the GHA→Semaphore mapping and conversion procedure; for Semaphore-side depth (cache CLI, test-results, blocks structure, sharding, promotions) defer to the linked skills. Use when the user asks to convert/port/migrate GitHub Actions to Semaphore, says "translate this workflow" or "convert ci.yml", or the repo has `.github/workflows/` and the user wants Semaphore instead. Can be invoked directly as `/sem-ai:gha-to-semaphore` (or via the broader `/sem-ai:init` orchestrator).
| 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 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.
sem-ai testbox warmup --project my-app
Returns a testbox ID + SSH info. The VM is ready when the command returns.
Options:
--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)
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.
sem-ai testbox ssh --id <testbox-id>
sem-ai testbox stop --id <testbox-id>
Or let it auto-expire after the duration/idle timeout.
run commands. Don't create a new testbox per test run.# 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