check-code-quality
You are performing static code quality analysis on the Scopy package: `$ARGUMENTS`
Run the same formatting and license checks that Scopy CI runs, scoped to a single package. This catches issues before pushing.
> /plugin marketplace add analogdevicesinc/scopy > /plugin install scopy_dev_plugin@scopy-plugins
How it fires
How this command gets triggered: by you, by Claude, or both.
/verify-packageContext preview
What this command does when you run it.
Run the same formatting and license checks that Scopy CI runs, scoped to a single package. This catches issues before pushing.
Run the same formatting and license checks that Scopy CI runs, scoped to a single package. This catches issues before pushing.
**Package to verify:** `$ARGUMENTS`
Run all 3 checks below against `scopy/packages/$ARGUMENTS/`. Report a clear pass/fail for each check with actionable fix instructions on failure.
Use the Glob tool to find all `.h`, `.hpp`, `.cpp`, `.cc` files in `scopy/packages/$ARGUMENTS/`, excluding:
For each file, run:
clang-format --dry-run --Werror --style=file:scopy/.clang-format <file>
This mirrors the CI job `check-cpp-formatting` in `scopy/.github/workflows/clang-format.yml`.
On failure, show the files that need formatting and tell the user to run:
clang-format -i --style=file:scopy/.clang-format <file>
Use the Glob tool to find all `CMakeLists.txt` and `*.cmake` files in `scopy/packages/$ARGUMENTS/`, excluding `build*/` directories.
For each file, run:
cmake-format --check --config-files scopy/.cmake-format <file>
On failure, show the files that need formatting and tell the user to run:
cmake-format -i --config-files scopy/.cmake-format <file>
Run the license scanner scoped to the package directory:
cd scopy && source tools/exclude_list.sh && \
tools/license-header/scan_missing_headers.sh \
--path packages/$ARGUMENTS \
--dirs "$(IFS=,; echo "${OMIT_DIRS_LIST[*]},${GITIGNORE_DIRS_LIST[*]}")" \
--files "$(IFS=,; echo "${OMIT_FILES_LIST[*]},${GITINORE_FILES_LIST[*]}")"On failure, show the files missing headers and tell the user to run:
cd scopy && ./tools/license.sh
After running all 3 checks, present a summary table:
## Package Verification: $ARGUMENTS | Check | Result | |--------------------|--------| | C++ Formatting | PASS/FAIL | | CMake Formatting | PASS/FAIL | | License Headers | PASS/FAIL |
For any FAIL, list the specific files and the fix command above.
You are performing static code quality analysis on the Scopy package: `$ARGUMENTS`
**Recommended model:** Opus — this command performs deep codebase exploration and multi-step reasoning to produce high-quality…
You are creating a JavaScript API class for a Scopy plugin so it can be controlled from test automation scripts.
You are creating JavaScript automated test scripts for a Scopy plugin, mapping RST manual test cases to API calls.
You are creating Sphinx RST documentation for a Scopy plugin user guide.
You are creating Sphinx RST test case documentation for a Scopy plugin, following the established test documentation format.