Add CoPilot skills

.github/copilot-instructions.md

@@ -31,14 +31,15 @@ These instructions define how GitHub Copilot should assist with this project. Th
 
 ## File Structure
 
-```txt
+```plaintext
 .azuredevops/ # Azure DevOps pipeline configuration and policy files.
 .github/      # GitHub Actions workflow files and linter configuration files.
 .nuget/       # NuGet package configuration files.
 build/        # Miscellaneous build files and scripts.
 DirectXMesh/  # DirectXMesh implementation files.
 Utilities/    # Utility headers such as a WaveFront .obj file loader and a FVF converter.
 Meshconvert/  # CLI tool for importing WaveFront .obj files and converting to CMO, SDKMESH, or VBO formats.
+skills/       # Published CoPilot skills for use by developers.
 Tests/        # Tests are designed to be cloned from a separate repository at this location.
 wiki/         # Local clone of the GitHub wiki documentation repository.
 ```
@@ -289,30 +290,4 @@ When reviewing documentation, do the following:
 
 ## Release Process
 
-1. Ensure all changes are merged into the `main` branch and that all tests pass.
-2. Git pull the local repository to ensure it is up to date with the `main` branch.
-3. Run the PowerShell script `build\preparerelease.ps1` which will generate a topic branch for the release, update the version number in `CMakeLists.txt`, the `README.md` file, the release notes in the nuspec files, and create a stub in the `CHANGELOG.md` file for the new release.
-4. Edit the `CHANGELOG.md` file to update it with a summary of changes.
-5. Submit the topic branch for review and merge into `main` once approved. Allow the GitHub Actions workflows and the Azure DevOps pipelines to complete successfully before proceeding.
-6. Run the PowerShell script `build\completerelease.ps1` which will set a tag on the project repo and the test repo, and create a release on GitHub with the release notes from `CHANGELOG.md`. Ensure you have set up GPG signing for your GitHub account so that the tags will be verified.
-7. Git pull the local repository to ensure it is up to date with the `main` branch. Be sure to include `--tags`.
-8. Push the `main` branch to the MSCodeHub mirror repository. Be sure to include `--tags`.
-9. Create a PR on MSCodeHub from the `main` branch to the `release` branch.
-10. Merge the PR on MSCodeHub to update the release branch, which will trigger the Azure DevOps pipeline to build signed binaries and the NuGet packages.
-11. Run the PowerShell script `build\downloadartifacts.ps1` to download the signed binaries from the Azure DevOps pipeline artifacts.
-12. Edit the GitHub release and upload the signed binaries to the release assets.
-13. Download the GitHub source .zip archive from the release. Unzip and compare to the local repo to ensure it matches — keep in mind there may be some CR/LF differences. Run minisign on the .zip to generate a signature file, and upload the signature file to the release assets.
-14. Validate the NuGet packages with <https://github.com/walbourn/contentexporter> by pushing the NuGet packages to a local Packages Source folder, updating the NuGet packages from that folder, and then build the project.
-15. Run the PowerShell script `build\promotenuget.ps1` with the `-Release` parameter to promote the version to the Release view on the project-scoped ADO feed.
-16. Run the MSCodeHub pipeline to publish the NuGet packages to nuget.org. The pipeline will automatically push the most recent package promoted to the Release view to nuget.org.
-17. Git pull a local repository of VCPKG to `d:\vcpkg` in sync with the `main` branch of the VCPKG repository.
-18. Run the PowerShell script `build\updatevcpkg.ps1` to update the DirectXMesh port in VCPKG with the new release version. This will edit the files in `ports\directxmesh`.
-19. Test the VCPKG port using all appropriate triplets and features.
-20. Run `.\vcpkg --x-add-version directxmesh` to update the VCPKG versioning history.
-21. Submit a PR to the VCPKG repository to update the DirectXMesh port back to the main GitHub repo. The PR will be reviewed and merged by the VCPKG maintainers.
-22. If relevant changes were made to the `meshconvert` tool, update the winget manifests for that tool in the `winget` repository.
-- Git pull a local repository to `D:\winget-pkgs` in sync with the `master` branch of the WinGet repository.
-- Run the PowerShell script `build\updatewinget.ps1` to update the winget manifests for the tool with the new release version.
-- Submit a PR to the `winget` repository to update the manifests for the tool.
-
-> When fully completed, be sure to update the GitHub release with links to the matching NuGet packages, the VCPKG port, and the winget manifests for the tools.
+The release process is documented in the [release skill](.github/skills/release/SKILL.md). Invoke the `release` skill for step-by-step guidance when performing a release.

.github/skills/release/SKILL.md

@@ -0,0 +1,83 @@
+---
+name: Release Process
+description: Guide for performing the DirectXMesh release process. Use this skill when asked to help with releasing a new version, publishing packages, or updating ports.
+---
+
+# Release Process
+
+## Prerequisites
+
+- All changes merged into the `main` branch with all tests passing.
+- GPG signing configured for your GitHub account (for verified tags).
+- Access to the MSCodeHub mirror repository and Azure DevOps pipelines.
+- Local repositories:
+  - VCPKG at `d:\vcpkg` (synced with `main` branch)
+  - WinGet at `D:\winget-pkgs` (synced with `master` branch, only if tool updates needed)
+- PATs will be needed for scripts that access GitHub and ADO.
+
+<!-- markdownlint-disable MD029 -->
+## Steps
+
+### Phase 1: Prepare Release
+
+1. Git pull the local repository to ensure it is up to date with the `main` branch.
+2. Run the PowerShell script `build\preparerelease.ps1` which will generate a topic branch for the release, update the version number in `CMakeLists.txt`, the `README.md` file, the release notes in the nuspec files, and create a stub in the `CHANGELOG.md` file for the new release.
+3. Edit the `CHANGELOG.md` file to update it with a summary of changes.
+4. Submit the topic branch for review and merge into `main` once approved. Allow the GitHub Actions workflows and the Azure DevOps pipelines to complete successfully before proceeding.
+
+### Phase 2: Tag and Create GitHub Release
+
+5. Run the PowerShell script `build\completerelease.ps1` which will set a tag on the project repo and the test repo, and create a release on GitHub with the release notes from `CHANGELOG.md`. Ensure you have set up GPG signing for your GitHub account so that the tags will be verified.
+6. Git pull the local repository to ensure it is up to date with the `main` branch. Be sure to include `--tags`.
+
+### Phase 3: MSCodeHub and Signed Binaries
+
+7. Push the `main` branch to the MSCodeHub mirror repository. Be sure to include `--tags`.
+8. Create a PR on MSCodeHub from the `main` branch to the `release` branch.
+9. Merge the PR on MSCodeHub to update the release branch, which will trigger the Azure DevOps pipeline to build signed binaries and the NuGet packages.
+10. Run the PowerShell script `build\downloadbuild.ps1` to download the signed binaries from the Azure DevOps pipeline artifacts.
+11. Edit the GitHub release and upload the signed binaries to the release assets.
+
+### Phase 4: Source Archive Signing
+
+12. Download the GitHub source .zip archive from the release. Unzip and compare to the local repo to ensure it matches — keep in mind there may be some CR/LF differences.
+13. Run minisign on the .zip to generate a signature file, and upload the signature file to the release assets.
+
+### Phase 5: NuGet Validation and Publishing
+
+14. Validate the NuGet packages with <https://github.com/walbourn/contentexporter> by pushing the NuGet packages to a local Packages Source folder, updating the NuGet packages from that folder, and then build the project.
+15. Run the PowerShell script `build\promotenuget.ps1 -Version <version> -Release` to promote the version to the Release view on the project-scoped ADO feed. The `-Version` parameter is required and should match the NuGet package version (e.g., `2026.6.2.1`).
+16. Run the MSCodeHub pipeline to publish the NuGet packages to nuget.org. The pipeline will automatically push the most recent package promoted to the Release view to nuget.org.
+
+### Phase 6: VCPKG Port Update
+
+17. Git pull a local repository of VCPKG to `d:\vcpkg` in sync with the `main` branch of the VCPKG repository.
+18. Run the PowerShell script `build\updatevcpkg.ps1` to update the DirectXMesh port in VCPKG with the new release version. This will edit the files in `ports\directxmesh`.
+    If the port includes patches, review them to determine if they should be removed or updated for the new release (the `updatevcpkg.ps1` script will warn about this).
+19. Test the VCPKG port using the script at `assets/vcpkgdxmesh.cmd` (in this skill folder). Copy it to `d:\vcpkg` and run from there after bootstrapping VCPKG.
+20. Run `.\vcpkg x-add-version directxmesh` to update the VCPKG versioning history.
+21. Submit a PR to the VCPKG repository to update the DirectXMesh port back to the main GitHub repo. The PR will be reviewed and merged by the VCPKG maintainers.
+
+### Phase 7: WinGet Manifests (Conditional)
+
+If relevant changes were made to the `meshconvert` tool:
+
+22. Git pull a local repository to `D:\winget-pkgs` in sync with the `master` branch of the WinGet repository.
+23. Run the PowerShell script `build\updatewinget.ps1` to update the winget manifests for the tool with the new release version.
+24. Submit a PR to the `winget` repository to update the manifests for the tool.
+
+### Phase 8: Finalize
+
+When fully completed, be sure to update the GitHub release with links to the matching NuGet packages, the VCPKG port, and the winget manifests for the tools.
+
+## Key Scripts
+
+| Script | Purpose |
+| --- | --- |
+| `build\preparerelease.ps1` | Creates topic branch, updates version numbers and changelog stub |
+| `build\completerelease.ps1` | Sets tags, creates GitHub release from changelog |
+| `build\downloadbuild.ps1` | Downloads signed binaries from Azure DevOps |
+| `build\promotenuget.ps1` | Promotes NuGet package to Release view on ADO feed |
+| `build\updatevcpkg.ps1` | Updates DirectXMesh VCPKG port files |
+| `assets\vcpkgdxmesh.cmd` | Tests VCPKG port across all triplets and features |
+| `build\updatewinget.ps1` | Updates winget manifests for CLI tools |

.github/skills/release/assets/vcpkgdxmesh.cmd

@@ -0,0 +1,153 @@
+@set VCPKG_BINARY_SOURCES=clear
+@set VCPKG_ROOT=%cd%
+@if %1.==xbox. goto xbox
+@if %1.==clang. goto clang
+.\vcpkg install directxmesh:x86-windows
+@if errorlevel 1 goto error
+.\vcpkg install directxmesh[tools]:x86-windows --recurse
+@if errorlevel 1 goto error
+.\vcpkg install directxmesh[dx12]:x86-windows --recurse
+@if errorlevel 1 goto error
+.\vcpkg install directxmesh[spectre]:x86-windows --recurse
+@if errorlevel 1 goto error
+.\vcpkg install directxmesh:x86-windows-static
+@if errorlevel 1 goto error
+.\vcpkg install directxmesh:x86-windows-static-md
+@if errorlevel 1 goto error
+.\vcpkg install directxmesh:x64-windows
+@if errorlevel 1 goto error
+.\vcpkg install directxmesh[tools]:x64-windows --recurse
+@if errorlevel 1 goto error
+.\vcpkg install directxmesh[dx12]:x64-windows --recurse
+@if errorlevel 1 goto error
+.\vcpkg install directxmesh[spectre]:x64-windows --recurse
+@if errorlevel 1 goto error
+.\vcpkg install directxmesh:x64-windows-static
+@if errorlevel 1 goto error
+.\vcpkg install directxmesh:x64-windows-static-md
+@if errorlevel 1 goto error
+.\vcpkg install directxmesh:arm64-windows
+@if errorlevel 1 goto error
+.\vcpkg install directxmesh[tools]:arm64-windows --recurse
+@if errorlevel 1 goto error
+.\vcpkg install directxmesh[spectre]:arm64-windows --recurse
+@if errorlevel 1 goto error
+.\vcpkg install directxmesh:arm64-windows-static
+@if errorlevel 1 goto error
+.\vcpkg install directxmesh:arm64-windows-static-md
+@if errorlevel 1 goto error
+.\vcpkg install directxmesh:arm64ec-windows
+@if errorlevel 1 goto error
+.\vcpkg install directxmesh[tools]:arm64ec-windows --recurse
+@if errorlevel 1 goto error
+.\vcpkg install directxmesh[spectre]:arm64ec-windows --recurse
+@if errorlevel 1 goto error
+.\vcpkg install directxmesh:x86-uwp
+@if errorlevel 1 goto error
+.\vcpkg install directxmesh:x64-uwp
+@if errorlevel 1 goto error
+.\vcpkg install directxmesh:arm64-uwp
+@if errorlevel 1 goto error
+@where /Q x86_64-w64-mingw32-g++.exe
+@if errorlevel 1 goto skipgcc64
+.\vcpkg install directxmesh:x64-mingw-dynamic
+@if errorlevel 1 goto error
+.\vcpkg install directxmesh[dx12]:x64-mingw-dynamic --recurse
+@if errorlevel 1 goto error
+.\vcpkg install directxmesh[tools]:x64-mingw-dynamic --recurse
+@if errorlevel 1 goto error
+.\vcpkg install directxmesh:x64-mingw-static
+@if errorlevel 1 goto error
+.\vcpkg install directxmesh[dx12]:x64-mingw-static --recurse
+@if errorlevel 1 goto error
+.\vcpkg install directxmesh[tools]:x64-mingw-static --recurse
+@if errorlevel 1 goto error
+:skipgcc64
+@where /Q i686-w64-mingw32-g++.exe
+@if errorlevel 1 goto skipgcc32
+.\vcpkg install directxmesh:x86-mingw-dynamic
+@if errorlevel 1 goto error
+.\vcpkg install directxmesh[dx12]:x86-mingw-dynamic --recurse
+@if errorlevel 1 goto error
+.\vcpkg install directxmesh[tools]:x86-mingw-dynamic --recurse
+@if errorlevel 1 goto error
+.\vcpkg install directxmesh:x86-mingw-static
+@if errorlevel 1 goto error
+.\vcpkg install directxmesh[dx12]:x86-mingw-static --recurse
+@if errorlevel 1 goto error
+.\vcpkg install directxmesh[tools]:x86-mingw-static --recurse
+@if errorlevel 1 goto error
+:skipgcc32
+@if "%GXDKLatest%."=="." goto finish
+:xbox
+.\vcpkg install directxmesh:x64-xbox-scarlett
+@if errorlevel 1 goto error
+.\vcpkg install directxmesh:x64-xbox-scarlett-static
+@if errorlevel 1 goto error
+.\vcpkg install directxmesh:x64-xbox-xboxone
+@if errorlevel 1 goto error
+.\vcpkg install directxmesh:x64-xbox-xboxone-static
+@if errorlevel 1 goto error
+@goto finish
+:clang
+.\vcpkg install directxmesh:x64-clangcl-dynamic
+@if errorlevel 1 goto error
+.\vcpkg install directxmesh[tools]:x64-clangcl-dynamic --recurse
+@if errorlevel 1 goto error
+.\vcpkg install directxmesh[dx12]:x64-clangcl-dynamic --recurse
+@if errorlevel 1 goto error
+.\vcpkg install directxmesh:x64-clangcl-static
+@if errorlevel 1 goto error
+.\vcpkg install directxmesh:arm64-clangcl-dynamic
+@if errorlevel 1 goto error
+.\vcpkg install directxmesh[tools]:arm64-clangcl-dynamic --recurse
+@if errorlevel 1 goto error
+.\vcpkg install directxmesh:arm64-clangcl-static
+@if errorlevel 1 goto error
+.\vcpkg install directxmesh:x64-clangcl-uwp
+@if errorlevel 1 goto error
+.\vcpkg install directxmesh:arm64-clangcl-uwp
+@if errorlevel 1 goto error
+@if "%GXDKLatest%."=="." goto finish
+.\vcpkg install directxmesh:x64-clangcl-scarlett
+@if errorlevel 1 goto error
+.\vcpkg install directxmesh:x64-clangcl-scarlett-static
+@if errorlevel 1 goto error
+.\vcpkg install directxmesh:x64-clangcl-xboxone
+@if errorlevel 1 goto error
+.\vcpkg install directxmesh:x64-clangcl-xboxone-static
+@if errorlevel 1 goto error
+:finish
+@echo SUCCEEDED
+@if %1.==xbox. goto eof
+@if %1.==clang. goto eof
+@echo .
+@echo . Run on x64-linux and arm64-linux
+@echo .   ./vcpkg install directxmesh
+@echo .   ./vcpkg install directxmesh[dx12] --recurse
+@where /Q x86_64-w64-mingw32-g++.exe
+@if NOT errorlevel 1 goto gcc64
+@echo .
+@echo . Run for MinGW64
+@echo .   .\vcpkg install directxmesh:x64-mingw-dynamic
+@echo .   .\vcpkg install directxmesh[dx12]:x64-mingw-dynamic --recurse
+@echo .   .\vcpkg install directxmesh[tools]:x64-mingw-dynamic --recurse
+@echo .   .\vcpkg install directxmesh:x64-mingw-static
+@echo .   .\vcpkg install directxmesh[dx12]:x64-mingw-static --recurse
+@echo .   .\vcpkg install directxmesh[tools]:x64-mingw-static --recurse
+:gcc64
+@where /Q i686-w64-mingw32-g++.exe
+@if NOT errorlevel 1 goto gcc32
+@echo .
+@echo . Run for MinGW32
+@echo .   .\vcpkg install directxmesh:x86-mingw-dynamic
+@echo .   .\vcpkg install directxmesh[dx12]:x86-mingw-dynamic --recurse
+@echo .   .\vcpkg install directxmesh[tools]:x86-mingw-dynamic --recurse
+@echo .   .\vcpkg install directxmesh:x86-mingw-dynamic
+@echo .   .\vcpkg install directxmesh[dx12]:x86-mingw-dynamic --recurse
+@echo .   .\vcpkg install directxmesh[tools]:x86-mingw-dynamic --recurse
+:gcc32
+@goto eof
+:error
+@echo FAILED
+:eof

.github/workflows/codeql.yml

@@ -59,7 +59,7 @@ jobs:
       - uses: ilammy/msvc-dev-cmd@0b201ec74fa43914dc39ae48a89fd1d8cb592756 # v1.13.0
 
       - name: Initialize CodeQL
-        uses: github/codeql-action/init@87557b9c84dde89fdd9b10e88954ac2f4248e463 # v3.29.5
+        uses: github/codeql-action/init@87557b9c84dde89fdd9b10e88954ac2f4248e463 # v4.36.1
         with:
           languages: c-cpp
           build-mode: manual
@@ -73,6 +73,6 @@ jobs:
         run: cmake --build out\build\x64-Debug
 
       - name: Perform CodeQL Analysis
-        uses: github/codeql-action/analyze@87557b9c84dde89fdd9b10e88954ac2f4248e463 # v3.29.5
+        uses: github/codeql-action/analyze@87557b9c84dde89fdd9b10e88954ac2f4248e463 # v4.36.1
         with:
           category: "/language:c-cpp"

.github/workflows/msvc.yml

@@ -65,6 +65,6 @@ jobs:
 
       # Upload SARIF file to GitHub Code Scanning Alerts
       - name: Upload SARIF to GitHub
-        uses: github/codeql-action/upload-sarif@87557b9c84dde89fdd9b10e88954ac2f4248e463 # v3.29.5
+        uses: github/codeql-action/upload-sarif@87557b9c84dde89fdd9b10e88954ac2f4248e463 # v4.36.1
         with:
           sarif_file: ${{ steps.run-analysis.outputs.sarif }}

.gitignore

@@ -31,3 +31,4 @@ x64
 /CMakeUserPresets.json
 /build/vcpkg_installed
 /build/*.exe
+!**/skills/**

README.md

@@ -38,10 +38,26 @@ These components are designed to work without requiring any content from the leg
 
   * Contains miscellaneous build files and scripts.
 
+* ``skills\``
+
+  * Contains published CoPilot skills for use by developers.
+
 ## Documentation
 
 Documentation is available on the [GitHub wiki](https://github.com/Microsoft/DirectXMesh/wiki).
 
+## CoPilot Usage
+
+For CoPilot CLI assistance with using DirectXMesh, try:
+
+```bash
+winget install GitHub.Copilot
+winget install GitHub.cli
+gh skill install microsoft/directxmesh
+copilot
+/skills list
+```
+
 ## Notices
 
 All content and source code for this package are subject to the terms of the [MIT License](https://github.com/microsoft/DirectXMesh/blob/main/LICENSE).