메뉴
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".
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.
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).
Initialize Semaphore CI/CD for the current repository — bootstrap the Semaphore project, write a working `.semaphore/semaphore.yml` (translating from GitHub Actions if present, or from scratch), wire required secrets, validate, and watch the first workflow. Applies Semaphore-side defaults automatically — agent image, toolbox CLIs, `test-results` epilogue rule, sharding heuristics — by routing through the linked skills. Use when the user wants to set up CI on Semaphore, says "initialize", "bootstrap CI", "prepare CI/CD for this project", "create a workflow on Semaphore", "make a `.semaphore` config", or runs `/sem-ai:init`.
| name | sem-ai-bootstrap |
| description | 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". |
The sem-ai plugin's MCP server, slash commands, and SessionStart update-check
hook all call the sem-ai Go binary. The plugin bundles only the manifest +
skills + slash-command markdown — the binary lives outside the plugin and
must be installed separately.
The user has installed the sem-ai plugin (via /plugin install sem-ai@semaphoreio)
but is hitting one of:
sem-ai binary not found on PATH. Install: ...Install the binary:
curl -fsSL https://raw.githubusercontent.com/semaphoreio/sem-ai/main/install.sh | sh
After install, they may need to add $HOME/.local/bin (or $HOME/.semaphore-ai/bin)
to their PATH — install.sh prints a hint on stderr when that's needed.
Then:
sem-ai connect <your-org>.semaphoreci.com <your-api-token>
Token is found at https://me.semaphoreci.com/account.
After binary install + token bootstrap, restart their AI host session (or reload the plugin) so the MCP server picks up the now-working binary.
If the user can already run sem-ai version from their shell, the binary
is installed. The issue is elsewhere — likely token / network / org context.
Direct them to sem-ai context list and sem-ai diagnose instead.