Menu
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Based on SOC occupation classification
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/ROCm/rocm-systems --skill validateThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Showing SKILL.md
| name | validate |
| description | Run full rocDecode build and test pipeline after code changes |
| allowed-tools | ["Bash(cmake *)","Bash(make *)","Bash(test/validate.sh *)","Bash(test/build_samples.sh *)","Bash(nproc)"] |
Run the full rocDecode validation pipeline. Execute these steps in order, stopping only
if a step fails. Run from the rocDecode project root (the directory containing this
repo's build/, samples/, and test/ directories).
IMPORTANT: Run each command as a SEPARATE Bash tool call. Do not chain commands with && or |.
The build derives its compiler, install prefix, and CTest data path from ROCM_PATH
(default /opt/rocm). If ROCm is installed elsewhere (e.g. a TheRock or custom build),
ROCM_PATH must be set. NOTE: skills run cmake in a NON-interactive shell that does not
source ~/.bashrc, so set ROCM_PATH in ~/.profile (or export it before launching Claude
Code) — otherwise the build silently falls back to /opt/rocm. Step 1 verifies this and
fails fast with guidance if the toolchain is missing.
Conformance test data (Phase 4) is located via the ROCDECODE_CONFORMANCE_DIR
environment variable, which defaults to $HOME/rocDecodeConformance. It must contain the
per-codec subdirectories AvcConformance, Av1Conformance, HevcConformance, and
Vp9Conformance. Codecs whose directory is missing are reported as WARNING and skipped,
so the pipeline still runs without the full data set.
Run: test/validate.sh --check-rocm
This confirms ROCM_PATH points at a usable ROCm install (the compiler exists) and that
the install prefix is writable before any build work — make install installs into
ROCM_PATH, so a read-only prefix like a system /opt/rocm would need sudo, which this
skill does not use. If it fails, fix ROCM_PATH (see the note above; point it at a
user-writable install) and re-run before continuing. Do not retry without changing
ROCM_PATH — if it cannot be resolved, stop and ask the developer.
The build/ directory is not checked into the repo, so on a fresh checkout it must be
created and configured first. cmake -B build -DENABLE_EXTENDED_TESTS=ON is idempotent —
it creates and configures build/ if missing, and is a cheap no-op if it is already
configured. -DENABLE_EXTENDED_TESTS=ON enables the additional FFmpeg-based CTest cases
(the CTest phase covers 6 tests without it, 15 with it); those extra tests are only added
when FFmpeg is found, so the flag is harmless on machines without FFmpeg.
Run these four commands separately:
cmake -B build -DENABLE_EXTENDED_TESTS=ONmake clean -C buildmake -j -C buildmake install -C build(make -j lets make choose parallelism without a $(nproc) command substitution,
which would otherwise trigger a permission prompt on every run.)
Run: test/build_samples.sh
Run: test/validate.sh
Report the final summary from validate.sh to the user.
Decode and triage HRR capture archives with full GPU replay by default (Linux). Builds hrr-playback when missing. On Windows: full native GPU replay via triage_archive.ps1 + ensure_playback.ps1 (PowerShell); Docker replay requires Linux or WSL2. Never edits source. Print finding summary in the chat reply.
Profiles a target application using rocprofv3 with program counter sampling enabled and then analyzes the results. Use when the user has a program that runs on an AMD GPU and asks to perform PC sampling, to determine the runtime performance characteristics of their application, to determine stall reasons, or to determine hotspots in the code.
Use when writing, planning, or improving unit tests for low-level transport or systems code — especially when reasoning about branch coverage, test gaps, identifying which uncovered paths are worth pursuing, or deciding when a feature's test suite is ready to merge.