[OPIK-6232] Improve skill performance#12
Draft
petrotiurin wants to merge 3 commits into
Draft
Conversation
![baz-reviewer[bot]](https://avatars.githubusercontent.com/in/933528?s=60&v=4){kind=small}
Comment on lines
+23
to
+27
| Run **all** of these discovery tasks in parallel — issue every read in a single batch, do not wait for one before starting the next: | ||
|
|
||
| Scan the codebase to determine: | ||
|
|
||
| 1. **Language**: Python (look for `*.py`, `pyproject.toml`, `requirements.txt`) or TypeScript (look for `*.ts`, `*.tsx`, `package.json`) | ||
| 2. **LLM frameworks in use** — search imports for these patterns: | ||
| 1. **Language**: Read `pyproject.toml`, `requirements.txt` (Python) or `package.json` (TypeScript) to confirm language. If none are present, list source files and identify the language from their extensions (`*.py` → Python, `*.ts` / `*.tsx` → TypeScript). | ||
| 2. **Existing Opik usage**: Read source files and look for `import opik` / `@opik.track`. **If already present, audit for completeness rather than re-instrumenting** — check that `entrypoint=True` exists, flush is present for scripts, and env config is set, then stop. | ||
| 3. **LLM frameworks**: Read source files and look for these import patterns: |
There was a problem hiding this comment.
The discovery checklist duplicates skills/opik/instrument-tracing.md and also short-circuits on import opik / @opik.track, skipping remediation steps for entrypoint=True, opik.flush_tracker(), and env config — should we replace this with a reference to the canonical skill instead?
Finding types: Code Dedup and Conventions Logical Bugs | Severity: 🟢 Low
Want Baz to fix this for you? Activate Fixer
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Generated description
Below is a concise technical summary of the changes proposed in this PR:
Restructure the Opik instrumentation guide to run discovery tasks (language/framework detection, call-graph scouting) in parallel while clarifying entrypoint decorator rules and integration application. Highlight environment setup, dependency guidance, and verification steps so the Opik workflow is consistently applied.
@opik.trackwithout double-tracing.Modified files (1)
Latest Contributors(2)
Modified files (1)
Latest Contributors(2)