Menu
Use when changing whisper.cpp, native build scripts, runtime artifact layout, or native runtime package contents.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Use when tests need deterministic model files, model downloads fail, or WHISPER_TEST_MODEL_PATH is involved.
Use when validating managed .NET changes that do not modify whisper.cpp or native runtime build outputs.
Use when changing Whisper.net managed C# APIs, processors, builders, tests, or examples without changing native runtime outputs.
Use when changing MAUI target frameworks, mobile runtime packaging, or mobile test behavior.
Use when changing CPU NoAvx runtime loading, package imports, or tests that must run without AVX.
Use when changing runtime selection, RuntimeOptions, NativeLibraryLoader, runtime package imports, or examples that force runtime order.
| name | Change native runtimes |
| description | Use when changing whisper.cpp, native build scripts, runtime artifact layout, or native runtime package contents. |
Use this skill when a task changes whisper.cpp, native build workflows, windows-scripts.ps1, Makefile, native dependency packaging, or files under runtimes/ that describe native runtime packages.
Do not validate these changes with downloaded preview native libs. Preview native libs are only a shortcut for managed-only validation. Native runtime changes must build or consume artifacts produced from the changed native inputs.
.github/workflows/*native-build.yml for the CI build matrix..github/workflows/build-all.yml and .github/workflows/upload-build-artifacts.yml for artifact aggregation and preview release publishing.windows-scripts.ps1 and Makefile for local native build entry points.runtimes/*.nuspec and runtimes/*/*.targets for package contents and MSBuild imports.tools/WhisperNetDependencyChecker/Program.cs for runtime load validation.From the repository root, dot-source the script and build only the relevant runtime when possible:
. .\windows-scripts.ps1
BuildWindows "Release"
BuildWindowsIntel "Release"
BuildWindowsArm "Release"
BuildWindowsAll "Release"
Use the specific function that matches the task. Do not rebuild every native runtime unless the change affects shared native build logic.
After placing built artifacts under runtimes/, validate native loading for the changed runtime:
dotnet run --project .\tools\WhisperNetDependencyChecker\WhisperNetDependencyChecker.csproj
dotnet run --project .\tools\WhisperNetDependencyChecker\WhisperNetDependencyChecker.csproj -- CpuNoAvx
dotnet run --project .\tools\WhisperNetDependencyChecker\WhisperNetDependencyChecker.csproj -- Cuda
dotnet run --project .\tools\WhisperNetDependencyChecker\WhisperNetDependencyChecker.csproj -- Cuda12
dotnet run --project .\tools\WhisperNetDependencyChecker\WhisperNetDependencyChecker.csproj -- Vulkan
dotnet run --project .\tools\WhisperNetDependencyChecker\WhisperNetDependencyChecker.csproj -- CoreML
dotnet run --project .\tools\WhisperNetDependencyChecker\WhisperNetDependencyChecker.csproj -- OpenVino
Only run checks for runtimes relevant to the change and available on the current machine.
When native package contents or targets change, also use the Validate runtime packages and releases skill before opening a PR.