Menu
xUnit analyzer warning meanings and examples
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Inspect, unpack, edit, sign, and repack Ren'Py save files. Use when working with Ren'Py .save archives, save metadata JSON, screenshot/extra_info/log/signatures entries, machine save-token keys, or when a user asks to modify or repair a Ren'Py savegame.
correct modelling of C# datastructures for maintainable code
Correctly call native (C/C++) libraries from .NET using P/Invoke and LibraryImport. Covers function signatures, string marshalling, memory lifetime, SafeHandle, and cross-platform patterns. USE FOR: writing new P/Invoke or LibraryImport declarations, reviewing or debugging existing native interop code, wrapping a C or C++ library for use in .NET, diagnosing crashes, memory leaks, or corruption at the managed/native boundary. DO NOT USE FOR: COM interop, C++/CLI mixed-mode assemblies, or pure managed code with no native dependencies.
Guides activity tracing with generated ActivitySources, tags, parent activities, exception status handling, and registration. Use when adding or reviewing OpenTelemetry activity tracing in Bendex flows.
Microsoft code analysis CA warning meanings and examples
Routing guide for enabled compiler and analyzer warnings in this Bendex solution
| name | xunit-warnings |
| description | xUnit analyzer warning meanings and examples |
Use this skill when the build reports enabled xUnit* diagnostics.
xUnit1013 - Public method should be marked as testWhat it flags: The analyzer reported code that violates the enabled project warning policy.
Example:
[Fact] or [Theory].