Use this agent when the user needs system design, API design, database schema changes, or architectural decisions. Triggers on requests for high-level technical design or cross-cutting concerns. Context: User planning a new feature user: "How should I design the new metrics aggregation system?" assistant: "I'll use…
Use this agent when builds fail and the user needs help fixing compilation errors. Triggers on Maven, npm, TypeScript, or Python build failures. Makes minimal changes to fix errors without refactoring. Context: Maven build failed user: "The build is failing, can you fix it?" assistant: "I'll use the build-fixer agent…
Use this agent when the user wants code reviewed, asks for feedback on changes, or before creating a PR. Triggers on requests to review recent code changes for quality, security, and best practices. Context: User finished implementing a feature user: "Review my changes" assistant: "I'll use the code-reviewer agent to…
Use this agent PROACTIVELY when users create, add, or modify rules, skills, agents, or MCPs. Also triggers on explicit audit requests. Ensures configuration follows best practices and prevents bloat. Context: User wants to add a new rule user: "Add a rule for error handling" assistant: "Before adding this, I'll use…
Use this agent when the user needs a detailed implementation plan for a complex feature or task. Triggers on multi-step features, refactoring efforts, or tasks with unclear scope. Context: User starting a complex feature user: "I need to implement experiment comparison functionality" assistant: "I'll use the planner…
Use this agent when the user wants to run tests and get results. Triggers on requests to execute test suites, check test status, or investigate test failures. Can run in background. Context: User wants to run tests user: "Run the backend tests" assistant: "I'll use the test-runner agent to execute the backend test…
Recipe for wiring a new linter into Opik's unified 🐙 Code Quality pipeline (pre-commit + CI). Use when adding a pre-commit-driven linter/formatter to the repo — enumerates every file that must change (.pre-commit-config.yaml, scripts/precommit-hook-descriptions.tsv, scripts/precommit-detect-hooks.py…
Add product analytics (BI) events to Opik features. Use when wiring events on the frontend, the backend, or the Python SDK - all three report through Segment to PostHog.
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…
Use when a developer wants an e2e test covering a change they just made — e.g. "explore this feature", "add a test for my PR", "cover the feature in PR.
Specification for instrumenting an opik-backend workflow with operational OpenTelemetry metrics — per-stage throughput/latency/error counters and native histograms, dimensioned per-customer (workspace). Use when a pipeline (scoring, ingestion, experiments, jobs) needs per-stage visibility. Covers metric emission only…
Build or update an Opik integration that lives OUTSIDE this repo — a standalone opik- package (e.g. opik-openclaw, opik-claude-code-plugin) or Opik support contributed into a third-party project (e.g. LiteLLM, Dify). Use ONLY when the user names an external repository or external package as the target; for…
Build, update, test, and document Opik SDK integrations (Python & TypeScript). Use when adding a new framework/provider integration under sdks/python/src/opik/integrations or sdks/typescript/src/opik/integrations, updating an existing one, or verifying that an integration logs traces correctly.
Use when building or extending a Page Object Model (POM) for the Opik E2E suite (under testsendtoend/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)…