[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F4WBZN94STF7KJN1WHDVRK":3,"skill-same:01M7F4WBZN94STF7KJN1WHDVRK":54},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7F4WBZN94STF7KJN1WHDVRK","release",null,"Releases .NET NuGet packages through a layered chain (library, MSBuild SDK, analyzers, consumers) without breaking restore. Use when publishing a package, bumping a lower-layer dependency in its consumers, moving a .NET SDK pin across repositories, choosing tag-driven versus push-driven publishing, setting up NuGet trusted publishing, or waiting for nuget.org to index a version before consumers restore it.","ANcpLua\u002Fancplua-dotnet","ANcpLua","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F124206820?v=4","01M6HB10NW8NGRV7W0N7WGZS7S","Alexander Nachtmann","01M7F4V3J3B3GGXPV413WXK8KX",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FANcpLua\u002Fancplua-dotnet\u002Fblob\u002Fmain\u002Fpackages\u002Fancplua-dotnet\u002Fskills\u002Frelease\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: release\ndescription: Releases .NET NuGet packages through a layered chain (library, MSBuild SDK, analyzers, consumers) without breaking restore. Use when publishing a package, bumping a lower-layer dependency in its consumers, moving a .NET SDK pin across repositories, choosing tag-driven versus push-driven publishing, setting up NuGet trusted publishing, or waiting for nuget.org to index a version before consumers restore it.\nlicense: Apache-2.0\ncompatibility: Needs git, gh, curl and the .NET SDK. scripts\u002Fwait-nuget.sh is POSIX shell.\n---\n\n# Layered NuGet release\n\nA consumer can only restore a version nuget.org has indexed. Pointing a version variable (SDK\ntruth, `Version.props`, `global.json` `msbuild-sdks`) at a version that isn't published and indexed\nfails every restore with NU1102. Release order follows the dependency graph, lowest layer first,\nand each layer waits for the one below it.\n\nANcpLua chain (lowest first):\n\n```text\nANcpLua.Roslyn.Utilities -> ANcpLua.Analyzers -> ANcpLua.NET.Sdk (injects the analyzers) -> consumers\n```\n\nTwo relations point in opposite directions, and both are true. For *publishing* the analyzers come\nbefore the SDK, as drawn above. For *building*, the analyzer repository uses the SDK, which is why\nits own agent contract draws `Roslyn.Utilities -> NET.Sdk -> Analyzers`.\n\nThe SDK's `Version.props` names the analyzer version every consumer gets, so the analyzers publish\nbefore the SDK points at them. The analyzer repository itself builds with the last published SDK\n(a deliberate one-version lag that breaks the cycle), and its self-reference variables point at\nits own last published version, never the one being built. Consumers move last, through\n`global.json` `msbuild-sdks`.\n\n## 1. Before touching versions\n\n- Read how each repository publishes (`.github\u002Fworkflows\u002F*publish*.yml`, `release.sh`, `Makefile`):\n  - **Tag-driven:** `on: push: tags: ['v*']`. You create and push the tag.\n  - **Push-driven:** `on: push: branches: [main]`. CI bumps the patch from the latest `v*` tag\n    and creates the tag itself. Don't tag by hand.\n  - **Manual:** a `release.sh` with an API key read from a file. Run it from a clean tree.\n- Look for a publish gate (\"no publishable changes since `\u003Ctag>` — skipping\"). A commit that changes\n  only `global.json`, docs or CI is often skipped on purpose. Don't force an identical package\n  through it.\n- The new version string must not exist yet:\n  `curl -s https:\u002F\u002Fapi.nuget.org\u002Fv3-flatcontainer\u002F\u003Cid-lowercase>\u002Findex.json`.\n\n## 2. Release one layer\n\n1. Make the change, update `CHANGELOG.md` and anything else that names the old version: docs,\n   templates, `global.json`, `Version.props`. Search for the old value across the repository.\n2. Run the repository's build, pack and test entrypoints the way CI does. For MSTest\n   execution, invoke the installed `mstest-extensions:mstest` skill; if unavailable,\n   report that gap and retain the repository's documented test entrypoint.\n   A broken commit must never reach a publishing branch or tag.\n3. Commit, push, then tag if publishing is tag-driven:\n   `git tag vX.Y.Z && git push origin vX.Y.Z`.\n4. Watch the publish run: `gh run list --workflow \u003Cfile> --limit 1`, then `gh run watch \u003Cid>`.\n5. Wait for the index with `scripts\u002Fwait-nuget.sh \u003CPackageId> \u003Cversion>`. It requires both the\n   flat container, which restore uses, and the registration leaf, which `PackageMetadataResource`\n   and many tools use. The flat container goes live first, often minutes before the registration\n   leaf.\n6. Only then point the next layer at the new version.\n\nA tag that points at a broken commit is never moved or deleted on the remote. Release the next\npatch instead.\n\nPack before tests in CI. `dotnet pack --no-build` ships whatever sits in the build output when it\nruns, and a test that builds or packs the repository's own projects (package-consumption tests,\nMSBuild integration tests) writes into that same output unless it gets its own\n`-p:ArtifactsPath=\u003Ctemp>\u002F`. ANcpLua.Roslyn.Utilities 3.0.0 and 3.0.1 shipped AssemblyVersion\n0.0.0.0 that way: a test packed `src\u002F` with `VersionPrefix=0.0.0` between build and pack. After\npacking, check one assembly per package: the version inside must be the release version. A green\nbuild plus correct `.nupkg` file names doesn't prove it.\n\n## 3. NuGet client caching\n\nThe NuGet client caches HTTP responses for 30 minutes (`~\u002F.local\u002Fshare\u002FNuGet\u002Fhttp-cache`). A\ntool that queried a package before its version was indexed keeps answering \"not found\" after\nthe index catches up. Re-run it with a throwaway cache:\n\n```bash\nNUGET_HTTP_CACHE_PATH=\"$(mktemp -d)\" dotnet run --project tools\u002FGenerator\n```\n\n`dotnet restore --no-http-cache` does the same for restore. Don't clear the user's caches to\nget past this.\n\n## 4. Publishing credentials\n\nOrder of preference:\n\n1. **Trusted publishing (OIDC).** The workflow has `permissions: id-token: write` and a\n   `NuGet\u002Flogin` step that exchanges the GitHub token for a short-lived API key\n   (`steps.login.outputs.NUGET_API_KEY`), configured on nuget.org per package owner,\n   repository and workflow file. There's no long-lived secret to rotate. The workflow file name\n   is part of the policy, so renaming the workflow breaks publishing.\n2. **A scoped API key in a CI secret.** Glob-scoped to the package prefix, push-only, with an\n   expiry.\n3. **A manual key file for local `release.sh` runs.** Read from a file whose location the\n   credential registry records (`vitals keys` on ANcpLua machines). Never paste a key into a\n   chat, a commit or a command line that ends up in shell history.\n\nWhen a publish fails with 403, check the key's glob and expiry, or the trusted-publishing policy's\nrepository and workflow name, before retrying.\n\n## 5. Moving consumers\n\nFor each consumer repository in the chain:\n\n1. `global.json`: `msbuild-sdks` to the new SDK version, `sdk.version` to the agreed .NET SDK.\n2. Remove repo-local overrides that the new SDK truth made equal or stale (see the\n   `nuget-versions` skill, section 1).\n3. Direct dependencies on lower layers (for example `ANcpLua.Roslyn.Utilities`) go to the new\n   version in their single central place. Read the release notes for moved or split packages.\n4. Build and test, commit, push, then release according to that repository's own mechanism.\n5. A repository with uncommitted work by someone else: work in a separate `git worktree` on\n   `origin\u002Fmain`, so the release commit contains only the version change.\n\n## 6. .NET SDK pins across machines\n\n- Install a new SDK through the machine's own channel (a dotfiles target, a package manager, or\n  `dotnet-install.sh --install-dir \u003Cthe existing root>`). Keep normal machine selection\n  predictable. If an isolated preview is requested, invoke the available\n  `ancplua-dotnet:nuget-versions` skill for SDK selection. Without it, report the\n  missing guidance rather than changing machine PATH or the stable release pin.\n- macOS: if an installer overwrites the `dotnet` host binary in place while the old one is still\n  mapped, the kernel kills every new `dotnet` process (exit 137, \"Killed: 9\") because the cached\n  code signature no longer matches the file. Delete the host binary and re-run the installer so\n  the file is created fresh. Don't patch the signature.\n- CI uses `actions\u002Fsetup-dotnet` with `global-json-file: global.json`, so the pin is the single\n  source.\n\n## 7. Report\n\nFor every layer, give the repository, commit, tag or version, publish run conclusion and index\nstatus, and for consumers the files changed. A layer whose gate skipped publishing is reported\nas \"committed, publish skipped by gate (`\u003Creason>`)\", not as released.\n","# Layered NuGet release\n\nA consumer can only restore a version nuget.org has indexed. Pointing a version variable (SDK\ntruth, `Version.props`, `global.json` `msbuild-sdks`) at a version that isn't published and indexed\nfails every restore with NU1102. Release order follows the dependency graph, lowest layer first,\nand each layer waits for the one below it.\n\nANcpLua chain (lowest first):\n\n```text\nANcpLua.Roslyn.Utilities -> ANcpLua.Analyzers -> ANcpLua.NET.Sdk (injects the analyzers) -> consumers\n```\n\nTwo relations point in opposite directions, and both are true. For *publishing* the analyzers come\nbefore the SDK, as drawn above. For *building*, the analyzer repository uses the SDK, which is why\nits own agent contract draws `Roslyn.Utilities -> NET.Sdk -> Analyzers`.\n\nThe SDK's `Version.props` names the analyzer version every consumer gets, so the analyzers publish\nbefore the SDK points at them. The analyzer repository itself builds with the last published SDK\n(a deliberate one-version lag that breaks the cycle), and its self-reference variables point at\nits own last published version, never the one being built. Consumers move last, through\n`global.json` `msbuild-sdks`.\n\n## 1. Before touching versions\n\n- Read how each repository publishes (`.github\u002Fworkflows\u002F*publish*.yml`, `release.sh`, `Makefile`):\n  - **Tag-driven:** `on: push: tags: ['v*']`. You create and push the tag.\n  - **Push-driven:** `on: push: branches: [main]`. CI bumps the patch from the latest `v*` tag\n    and creates the tag itself. Don't tag by hand.\n  - **Manual:** a `release.sh` with an API key read from a file. Run it from a clean tree.\n- Look for a publish gate (\"no publishable changes since `\u003Ctag>` — skipping\"). A commit that changes\n  only `global.json`, docs or CI is often skipped on purpose. Don't force an identical package\n  through it.\n- The new version string must not exist yet:\n  `curl -s https:\u002F\u002Fapi.nuget.org\u002Fv3-flatcontainer\u002F\u003Cid-lowercase>\u002Findex.json`.\n\n## 2. Release one layer\n\n1. Make the change, update `CHANGELOG.md` and anything else that names the old version: docs,\n   templates, `global.json`, `Version.props`. Search for the old value across the repository.\n2. Run the repository's build, pack and test entrypoints the way CI does. For MSTest\n   execution, invoke the installed `mstest-extensions:mstest` skill; if unavailable,\n   report that gap and retain the repository's documented test entrypoint.\n   A broken commit must never reach a publishing branch or tag.\n3. Commit, push, then tag if publishing is tag-driven:\n   `git tag vX.Y.Z && git push origin vX.Y.Z`.\n4. Watch the publish run: `gh run list --workflow \u003Cfile> --limit 1`, then `gh run watch \u003Cid>`.\n5. Wait for the index with `scripts\u002Fwait-nuget.sh \u003CPackageId> \u003Cversion>`. It requires both the\n   flat container, which restore uses, and the registration leaf, which `PackageMetadataResource`\n   and many tools use. The flat container goes live first, often minutes before the registration\n   leaf.\n6. Only then point the next layer at the new version.\n\nA tag that points at a broken commit is never moved or deleted on the remote. Release the next\npatch instead.\n\nPack before tests in CI. `dotnet pack --no-build` ships whatever sits in the build output when it\nruns, and a test that builds or packs the repository's own projects (package-consumption tests,\nMSBuild integration tests) writes into that same output unless it gets its own\n`-p:ArtifactsPath=\u003Ctemp>\u002F`. ANcpLua.Roslyn.Utilities 3.0.0 and 3.0.1 shipped AssemblyVersion\n0.0.0.0 that way: a test packed `src\u002F` with `VersionPrefix=0.0.0` between build and pack. After\npacking, check one assembly per package: the version inside must be the release version. A green\nbuild plus correct `.nupkg` file names doesn't prove it.\n\n## 3. NuGet client caching\n\nThe NuGet client caches HTTP responses for 30 minutes (`~\u002F.local\u002Fshare\u002FNuGet\u002Fhttp-cache`). A\ntool that queried a package before its version was indexed keeps answering \"not found\" after\nthe index catches up. Re-run it with a throwaway cache:\n\n```bash\nNUGET_HTTP_CACHE_PATH=\"$(mktemp -d)\" dotnet run --project tools\u002FGenerator\n```\n\n`dotnet restore --no-http-cache` does the same for restore. Don't clear the user's caches to\nget past this.\n\n## 4. Publishing credentials\n\nOrder of preference:\n\n1. **Trusted publishing (OIDC).** The workflow has `permissions: id-token: write` and a\n   `NuGet\u002Flogin` step that exchanges the GitHub token for a short-lived API key\n   (`steps.login.outputs.NUGET_API_KEY`), configured on nuget.org per package owner,\n   repository and workflow file. There's no long-lived secret to rotate. The workflow file name\n   is part of the policy, so renaming the workflow breaks publishing.\n2. **A scoped API key in a CI secret.** Glob-scoped to the package prefix, push-only, with an\n   expiry.\n3. **A manual key file for local `release.sh` runs.** Read from a file whose location the\n   credential registry records (`vitals keys` on ANcpLua machines). Never paste a key into a\n   chat, a commit or a command line that ends up in shell history.\n\nWhen a publish fails with 403, check the key's glob and expiry, or the trusted-publishing policy's\nrepository and workflow name, before retrying.\n\n## 5. Moving consumers\n\nFor each consumer repository in the chain:\n\n1. `global.json`: `msbuild-sdks` to the new SDK version, `sdk.version` to the agreed .NET SDK.\n2. Remove repo-local overrides that the new SDK truth made equal or stale (see the\n   `nuget-versions` skill, section 1).\n3. Direct dependencies on lower layers (for example `ANcpLua.Roslyn.Utilities`) go to the new\n   version in their single central place. Read the release notes for moved or split packages.\n4. Build and test, commit, push, then release according to that repository's own mechanism.\n5. A repository with uncommitted work by someone else: work in a separate `git worktree` on\n   `origin\u002Fmain`, so the release commit contains only the version change.\n\n## 6. .NET SDK pins across machines\n\n- Install a new SDK through the machine's own channel (a dotfiles target, a package manager, or\n  `dotnet-install.sh --install-dir \u003Cthe existing root>`). Keep normal machine selection\n  predictable. If an isolated preview is requested, invoke the available\n  `ancplua-dotnet:nuget-versions` skill for SDK selection. Without it, report the\n  missing guidance rather than changing machine PATH or the stable release pin.\n- macOS: if an installer overwrites the `dotnet` host binary in place while the old one is still\n  mapped, the kernel kills every new `dotnet` process (exit 137, \"Killed: 9\") because the cached\n  code signature no longer matches the file. Delete the host binary and re-run the installer so\n  the file is created fresh. Don't patch the signature.\n- CI uses `actions\u002Fsetup-dotnet` with `global-json-file: global.json`, so the pin is the single\n  source.\n\n## 7. Report\n\nFor every layer, give the repository, commit, tag or version, publish run conclusion and index\nstatus, and for consumers the files changed. A layer whose gate skipped publishing is reported\nas \"committed, publish skipped by gate (`\u003Creason>`)\", not as released.\n",{"name":5,"license":15,"description":7,"compatibility":24},"Needs git, gh, curl and the .NET SDK. scripts\u002Fwait-nuget.sh is POSIX shell.","main","703474adbca925ced1bb614d1d53a21dd9125e4b","packages\u002Fancplua-dotnet\u002Fskills\u002Frelease",0,"https:\u002F\u002Fgithub.com\u002FANcpLua\u002Fancplua-dotnet","https:\u002F\u002Fgithub.com\u002FANcpLua","SWE Student ","Ein Tag lehrt den anderen.       \r\n    ♉🍏🐍 \r\n","2026-11-10 12:15:27",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add ANcpLua\u002Fancplua-dotnet --skill release",{"tool":40,"command":41},"bunx","bunx skills add ANcpLua\u002Fancplua-dotnet --skill release",{"tool":43,"command":44},"pnpm","pnpm dlx skills add ANcpLua\u002Fancplua-dotnet --skill release","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FANcpLua\u002Fancplua-dotnet\u002Fblob\u002Fmain\u002Fpackages\u002Fancplua-dotnet\u002Fskills\u002Frelease\u002FSKILL.md",true,[48],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"scripts\u002Fwait-nuget.sh","SCRIPT","脚本",1290,"https:\u002F\u002Fgithub.com\u002FANcpLua\u002Fancplua-dotnet\u002Fblob\u002Fmain\u002Fpackages\u002Fancplua-dotnet\u002Fskills\u002Frelease\u002Fscripts\u002Fwait-nuget.sh",[55,64,71,78,85,92],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":59,"licenseFileUrl":60,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M7F4X02P5FFKPX5MQPHKFJGY","csharp-union-types","Design, review and implement C# 15 unions and closed hierarchies in .NET 11 code. Use for union declarations, custom [Union] types, exhaustive matching, default\u002Fnull handling and union serialization. Do not upgrade earlier frameworks or replace working inheritance merely because unions exist.","MIT","https:\u002F\u002Fgithub.com\u002FANcpLua\u002Fancplua-dotnet\u002Fblob\u002Fmain\u002Fpackages\u002Fnami\u002Fplugins\u002Fnami\u002Fskills\u002Fcsharp-union-types\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FANcpLua\u002Fancplua-dotnet\u002Fblob\u002Fmain\u002Fpackages\u002Fnami\u002Fplugins\u002Fnami\u002Fskills\u002Fcsharp-union-types\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7F4W5B0G7ENQ1E8136T5BRY","performance","Investigate .NET runtime performance using logs, metrics, traces, spans and profiles; collect crash\u002Fhang diagnostics. Use for CPU, GC, allocation or latency problems, hot-path reviews and BenchmarkDotNet comparisons. MSBuild timing belongs to msbuild; MSTest execution belongs to mstest-extensions.","https:\u002F\u002Fgithub.com\u002FANcpLua\u002Fancplua-dotnet\u002Fblob\u002Fmain\u002Fpackages\u002Fancplua-dotnet\u002Fskills\u002Fperformance\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7F4W0T0N9V8T6JPP3MN5V4P","nuget-versions","Manage .NET package and SDK versions, CPM migrations, Version.props ownership, global.json pins, isolated SDK installations and Renovate updates. Use for package bumps, conflicting or missing versions, NuGet restore errors and SDK selection. MSTest runner\u002Fprofile semantics belong to mstest-extensions.","https:\u002F\u002Fgithub.com\u002FANcpLua\u002Fancplua-dotnet\u002Fblob\u002Fmain\u002Fpackages\u002Fancplua-dotnet\u002Fskills\u002Fnuget-versions\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7F4VW470PY61YBE70VZ0XMY","msbuild","Writes and reviews MSBuild evaluation, properties, items, imports, custom targets and build\u002FbuildTransitive package assets for SDK-style .NET repositories. Use for ignored or empty properties\u002Fitems, generated files, analyzer\u002Fbuild-asset packaging, build-file reviews, binlog diagnosis and incremental-build problems. Focused MSTest project setup, runner configuration and test commands belong to mstest-extensions.","https:\u002F\u002Fgithub.com\u002FANcpLua\u002Fancplua-dotnet\u002Fblob\u002Fmain\u002Fpackages\u002Fancplua-dotnet\u002Fskills\u002Fmsbuild\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7F4VRXB35HECDMZR0SVK7DA","csharp-refactoring","Refactor C# and reconcile stale constants, dead checks and abandoned code, including indirect production uses. Use for renames, moves, deduplication, exhaustive cleanup, generated declarations and runtime\u002FAPI contracts. MSTest test design and review belong to mstest-extensions.","https:\u002F\u002Fgithub.com\u002FANcpLua\u002Fancplua-dotnet\u002Fblob\u002Fmain\u002Fpackages\u002Fancplua-dotnet\u002Fskills\u002Fcsharp-refactoring\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M7F4VM8GMZ0ZB4STXWFZCB69","audit","Audits one or more .NET repositories for build, package and analyzer problems and separates certain fixes from judgment calls. Use for repository or fleet build-policy audits, shared SDK\u002Fpackage consistency and cross-repository version rollouts. Focused MSTest setup, execution and test-quality reviews belong to mstest-extensions.","https:\u002F\u002Fgithub.com\u002FANcpLua\u002Fancplua-dotnet\u002Fblob\u002Fmain\u002Fpackages\u002Fancplua-dotnet\u002Fskills\u002Faudit\u002FSKILL.md",[],[]]