Menú
Local development environment setup and commands. Use when helping with dev server, Docker, or local testing.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Use when a developer wants to add, write, or create an end-to-end test for an Opik feature, page, or branch — e.g. "add an e2e test for the experiments comparison page", "write a test for the feature I just built", "e2e test for this branch", "cover the dataset items flow with a test". Runs the full loop in tests_end_to_end/e2e/ — analyze the feature and frontend code, explore the live UI with the Playwright MCP, write the Page Object Model + spec, and run it locally until green.
Use when an Opik E2E test has failed and a developer wants it investigated — e.g. "why did this e2e test fail?", "investigate the failing run on my PR", "is dataset-crud-smoke flaky?", "the nightly e2e suite went red". Takes a failure from a CI check, a TestOps launch, a test name, or a local run; gathers the trace and history, classifies regression vs. flake, and proposes a fix. Read-only — it diagnoses and proposes, it does not edit tests.
Use when building or extending a Page Object Model (POM) for the Opik E2E suite (under `tests_end_to_end/e2e/pom/`) and you need to choose stable selectors against the live UI. Walks through seeding required state, exploring the running page with the Playwright MCP (accessibility snapshot + data-testid enumeration), picking the most stable locator for each element, and verifying it before committing. Used as the discovery sub-step by the `writing-e2e-tests` skill.
Java backend patterns for Opik. Use when working in apps/opik-backend, designing APIs, database operations, or services.
React frontend patterns for Opik. Use when working in apps/opik-frontend, on components, state, or data fetching.
Python SDK patterns for Opik. Use when working in sdks/python, on SDK APIs, integrations, or message processing.
| name | local-dev |
| description | Local development environment setup and commands. Use when helping with dev server, Docker, or local testing. |
./scripts/dev-runner.sh --restart # First time / full rebuild
./scripts/dev-runner.sh --start # Daily start (no rebuild)
./scripts/dev-runner.sh --stop # Stop everything
./scripts/dev-runner.sh --verify # Check status
| Mode | Command | Frontend | Use When |
|---|---|---|---|
| Standard | --restart | localhost:5174 | Frontend work, full-stack |
| BE-only | --be-only-restart | localhost:5173 | Backend-focused, faster rebuilds |
./scripts/dev-runner.sh --build-be # Backend only
./scripts/dev-runner.sh --build-fe # Frontend only
./scripts/dev-runner.sh --lint-be # Spotless
./scripts/dev-runner.sh --lint-fe # ESLint
./scripts/dev-runner.sh --migrate # DB migrations
tail -f /tmp/opik-backend.log # Backend
tail -f /tmp/opik-frontend.log # Frontend (standard)
docker logs -f opik-frontend-1 # Frontend (BE-only)
export OPIK_URL_OVERRIDE='http://localhost:8080'
export OPIK_WORKSPACE='default'
Won't start:
./scripts/dev-runner.sh --verify
lsof -i :8080 # Port conflict?
./scripts/dev-runner.sh --stop && ./scripts/dev-runner.sh --restart
Build fails:
cd apps/opik-backend && mvn clean install -DskipTests
cd apps/opik-frontend && rm -rf node_modules && npm install
Database issues:
./scripts/dev-runner.sh --stop
./opik.sh --clean # WARNING: deletes data
./scripts/dev-runner.sh --restart