菜单
Enable trimming and AOT publishing on .NET executable projects in the correct staged order. Use when working on a .NET project that produces a publishable executable (OutputType=Exe or WinExe), or when asked to enable PublishTrimmed, PublishAot, or fix IL2xxx/IL3xxx warnings.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | credfeto-dotnet-publish |
| description | Enable trimming and AOT publishing on .NET executable projects in the correct staged order. Use when working on a .NET project that produces a publishable executable (OutputType=Exe or WinExe), or when asked to enable PublishTrimmed, PublishAot, or fix IL2xxx/IL3xxx warnings. |
When working on a .NET project that produces a publishable executable (OutputType=Exe or OutputType=WinExe), follow these steps in order.
Add <PublishTrimmed>true</PublishTrimmed> to the project file and verify the project builds without trim warnings or errors.
IL2xxx trim-analysis warnings before committing.JsonSerializer usage with a JsonSerializerContext annotated with [JsonSerializable].[DynamicallyAccessedMembers] only where reflection is genuinely unavoidable and cannot be replaced with a source generator.<TreatWarningsAsErrors>true</TreatWarningsAsErrors>.Once <PublishTrimmed>true</PublishTrimmed> builds without warnings, replace it with <PublishAot>true</PublishAot> (AOT implies trimming; both properties do not need to be set simultaneously).
IL3xxx AOT-compatibility warnings.Emit, DynamicMethod, Expression.Compile, CSharpCodeProvider, etc.IsAotCompatible=true in the package metadata or a corresponding [RequiresUnreferencedCode] annotation indicating the incompatibility.Raise a GitHub issue in the current repository describing the incompatibility (package name, version, and the specific warning or error), then stop. Do not work around the incompatibility by suppressing warnings or downgrading the property.
<TreatWarningsAsErrors>true</TreatWarningsAsErrors>.#pragma warning disable <ID>, <NoWarn>, <WarningsNotAsErrors>, or [SuppressMessage] without explicit written permission from the repo owner.Triage deprecation warnings seen in test output — fix ones caused by your change immediately, track pre-existing ones with a GitHub issue. Use whenever a deprecation warning (framework or runtime warning about a deprecated API) appears while running tests.
Write .NET unit tests using FunFair.Test.Common/FunFair.Test.Infrastructure base classes, mocking helpers, date sources, and xunit assertion patterns instead of hand-rolled equivalents. Use whenever writing or reviewing a .NET unit test (a *.Tests project).
Create, name, and maintain git branches — branching rules, Conventional Commits-style branch naming, rebasing against main, resuming interrupted work, and resolving version conflicts in dependency manifests during merges/rebases. Use when starting new work, creating a branch, resuming work on an existing branch, rebasing, or resolving merge conflicts.
Commit and push changes safely — branch checks, build/test gates, Conventional Commits format, and push cadence. Use whenever about to commit, stage, or push changes in any repository, or when acting as the Committer agent.
Create and manage GitHub issues correctly — duplicate search, planned descriptions, priority/status labels, assignment, and the Blocked label rules for AI-initiated issues, including the mandatory tracking issue required before starting any ad-hoc task. Use when asked to create a GitHub issue, when raising an issue autonomously, when a human asks you to do something and no existing issue or PR is already specified, when a PR or issue comment asks you to raise an issue, when selecting the next issue to work on, or when asking a blocking question and needing to mark an item Blocked.
Design and optimise performance-critical code, and back optimisations with committed benchmarks and measured allocation thresholds. Use when writing or optimising performance-critical code, or when asked to add or update a benchmark.