OpenParable
Skip to content
← Back to skills

Ov Ensure Coding Style

Testing & Quality
ov-ensure-coding-style

Ov Ensure Coding Style 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.

Detect and fix clang-format, clang-tidy, and copyright header violations in an OpenVINO C++ codebase. Use when the user complains about code style or formatting, asks to clean up changes, fix linting, add a copyright header, or when a style check or linting CI job is failing. Do not use for build errors, compilation failures, linker errors, test failures, runtime crashes, accuracy issues, or CMake config problems.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/openvinotoolkit/openvino/blob/HEAD/.claude/skills/ov-ensure-coding-style/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/ov-ensure-coding-style, 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.

Apply Code Standards

Iteratively detect and fix all clang-format, clang-tidy, and copyright violations introduced by the current branch's changes.

Step 1: Identify Affected Files and Build Targets

Before running any commands, check whether the upstream reference is already confirmed in the conversation. If it is not, stop and ask:

"I'll diff against upstream/master. Let me know if you use a different upstream."

Do not proceed until the user replies. Use the confirmed reference <ref_branch> in all subsequent steps. Once the upstream branch is known, you must fetch <ref_branch> and find a merge-base commit <ref_commit>, against which the diff should be collected. Then run:

git diff --name-only <ref_commit> | grep -v '^thirdparty' | tee /tmp/changed_files.txt

Map the changed files to CMake targets. If the mapping is not obvious, ask the user:

"Which CMake targets cover the files you changed? (e.g., openvino_intel_cpu_plugin)"

Step 2: Check, Fix, Repeat

Follow the fix order and tool instructions from coding_style.md exactly — do not rearrange or skip steps. Read that file before proceeding. Repeat the full cycle until all checks pass.