Ov Debug
Testing & Qualityov-debugOv Debug is an Agent Skill for testing & quality published in the openvinotoolkit/openvino repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Troubleshooting all sorts of failures, crashes, exceptions and errors using debug capabilities. Analyze accuracy, performance, model compilation, or memory issues. Dump tensors and intermediate blobs. Serialize and visualize IRs, execution graphs. Enable verbose, logging. Profile execution. Compare layer outputs. Inspect, trace or dump transformations. Identify executed operations, nodes, primitives, kernels.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/openvinotoolkit/openvino/blob/HEAD/.claude/skills/ov-debug/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/ov-debug, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Debug Skill
Prerequisites
Build flags that enable debug capabilities (check CMakeCache.txt in the build dir):
-DENABLE_DEBUG_CAPS=ON— CPU/GPU plugin debug env vars, transformation matcher logging
Components
| Component | Reference file to read | Routing hints |
|---|---|---|
| openvino_intel_cpu_plugin | @components/debug-intel-cpu-plugin.md | CPU: inference issues, wrong results, slow inference, tensor dumps, execution graphs |
| openvino_intel_gpu_plugin | @components/debug-intel-gpu-plugin.md | GPU: inference issues, wrong results, slow inference, tensor dumps, execution graphs |
| transformations | @components/debug-transformations.md | transformation not applied, pass not firing, slow compilation, graph inspection |
Steps
- Match the user's symptom to the routing hints above to identify the component(s)
- Load the component's reference file
- Follow the instructions and recommendations for debugging