ov-ensure-coding-style
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.
来源信息
- 仓库
- openvinotoolkit/openvino
- 最近来源活动
- 2026年5月4日 17:00
- 检测到的 SKILL.md 语言
- 英语
- 星标
- 10,981
- 分支
- 3,434
安装方式
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
检查来源文件
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
正在显示 SKILL.md
SKILL.md
来源说明 · 只读预览- name
- ov-ensure-coding-style
- description
- 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.
# 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:
```bash
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](../../../docs/dev/coding_style.md) exactly — do not rearrange or skip steps.** Read that file before proceeding. Repeat the full cycle until all checks pass.
在 GitHub 查看