dotnet-powershell
暂无简介
- License 许可
- Apache-2.0
- 所属仓库
- iokaio/vcp
- 最近更新
- 2026-10-06
- Stars
- ★ 0
- Forks
- 0
02 资源文件 1
- 参考文档skill.json706 B
03 SKILL.md 正文
.NET and PowerShell on Windows
Original VCP guidance.
Read the project
*.slnor*.slnx: which projects belong to the build and their configurations.*.csproj,*.fsproj,*.vbproj:TargetFramework(s),Sdkattribute (SDK-style) or legacy format,IsPackable, test framework references (xUnit, NUnit, MSTest),InternalsVisibleTo.Directory.Build.propsandDirectory.Build.targets: shared properties such asTreatWarningsAsErrors,Nullable, analyzers andLangVersion.Directory.Packages.props: central package version management.global.json: SDK pin and roll-forward policy. It does not prove that every project supports the installed SDK.NuGet.config: package sources; private feeds may need credentials you do not have..editorconfig: formatting and analyzer severity.- PowerShell: module manifests (
*.psd1),#Requiresstatements, parameter validation, module dependencies,PSScriptAnalyzerSettings.psd1, and Pester tests (*.Tests.ps1) and configuration.
Root *.sln, *.slnx, *.csproj, *.fsproj, *.vbproj and global.json files are detected. Nested-only projects and PowerShell-only repositories are not yet detected; the user can activate it with /skills activate <id> (the ID /skills list shows) or vcp run --skill <id>.
Discover commands in this order
- Project-declared tasks: build scripts (
build.ps1,build.cmd, Cake, Nuke, Invoke-Build or psake),Makefile, CI workflow files, CONTRIBUTING and AGENTS.md. - Ecosystem defaults, only when the project supports them. Candidates to confirm:
dotnet build <project-or-solution> -c <config> --no-restore;dotnet test <test-project> --no-restore --filter <expression>;dotnet format --verify-no-changes --no-restorewhen the project uses it;Invoke-Pester -Path <tests>with the repository's declared configuration;Invoke-ScriptAnalyzerwhen configured.
dotnet build, test, format and run restore implicitly unless given --no-restore, and restore contacts NuGet feeds, possibly private feeds with stored credentials. Pass --no-restore by default when obj/project.assets.json exists for the projects involved; otherwise treat dotnet restore as a separate network effect needing authority and report dependent checks as not run. Module installation (Install-Module, Install-PSResource) also requires separate authority.
Toolchain variants
- SDK-style projects build with
dotnet; legacy (non-SDK) projects and some .NET Framework targets need MSBuild from Visual Studio and may not build on other hosts. - Multi-targeted projects build and test once per framework; narrow with
-f <tfm>when appropriate. - Windows PowerShell 5.1 (
powershell.exe, .NET Framework) and PowerShell 7 (pwsh, .NET) differ in cmdlets, default encodings, operators and module compatibility. Honor#Requires -VersionandPSEdition. - Pester major versions differ in configuration and assertion syntax; follow the version the tests are written for.
Engineering rules
Preserve target frameworks and solution structure. Treat paths as data: use -LiteralPath for filesystem operations and correct argument passing; do not construct command text from repository strings. Review native exit codes ($LASTEXITCODE) separately from PowerShell exceptions, pipeline behavior, and terminating versus nonterminating errors.
Verification evidence
Run the narrowest affected test project or filter first, then the solution when shared code changed. Include analyzer warnings the project treats as errors. Record the exact SDK or shell edition, project, configuration, target framework and observed results. Missing SDKs, workloads, modules or Windows components mean those checks were not run.
Pitfalls
- A test run that discovers zero tests is not a pass; check the adapter and filter.
- Running test hosts,
dotnet build-serverprocesses, IDEs and antivirus lockbinandobjoutputs; stop the process rather than deleting outputs. - Stale
objstate after switching configuration or framework can cause misleading errors. - Execution policy can block scripts; do not change it without authority.
- Quoting: single quotes are literal, double quotes expand
$and backtick escapes; native command argument passing differs between editions.--%and splatting change parsing. Write-Hostoutput is not pipeline output; functions return everything they emit.- Case-insensitive paths,
\separators, CRLF line endings, and legacy path length limits. Windows PowerShell 5.1 reads BOM-less scripts in the ANSI code page, so non-ASCII scripts may need a UTF-8 BOM.
Authority: this guidance ranks below current user constraints and AGENTS.md, grants no tools, installs or network access, and missing prerequisites are reported as not run.
04 同仓库更多 Skills
skill-installer
Install Codex skills into $CODEX_HOME/skills from a curated list or a GitHub repo path. Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo (including private repos).
skill-creator
Create or update a Codex skill with appropriately scoped instructions and any needed supporting resources.
review-agent
Perform a read-only, defect-first review of a specified code change and return every actionable finding. Use when another agent delegates review of uncommitted changes, a base-branch diff, a commit, or custom review instructions.
plugin-creator
Create and scaffold plugin directories for Codex with a required `.codex-plugin/plugin.json`, optional plugin folders/files, valid manifest defaults, and personal-marketplace entries by default. Use when Codex needs to create a new personal plugin, add optional plugin structure, generate or update marketplace entries for plugin ordering and availability metadata, or update an existing local plugin during development with the CLI-driven cachebuster and reinstall flow.
openai-docs
Use for Codex models/pricing, scheduled tasks, skills, settings, setup, troubleshooting, customization, automations, and self-knowledge—including 'you,' 'your,' 'this app,' or 'this coding agent' when they refer to Codex—and for OpenAI APIs/products and ChatGPT Work. Also use for model choice/migration, prompting, SDKs, Responses, Realtime, agents, evals, and Chat/Work/Codex comparisons. Do not use for generic app/software tasks that merely mention Codex.
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output should be a bitmap asset rather than repo-native code or vector. Do not use when the task is better handled by editing existing SVG/vector/code-native assets, extending an established icon or logo system, or building the visual directly in HTML/CSS/canvas.