Skip to content
cccskills
FreePublished on GitHub

code-review

Review .NET changes for bugs, regressions, architectural drift, missing tests, incorrect async or disposal behavior, and platform-specific pitfalls before you approve or merge them. USE FOR: reviewing a pull request or patch in a .NET repository; checking for behavioral regressions, API misuse, or missing tests; auditing architectural or framework-specific. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.

The English summary is being prepared. Showing the original description.

managedcode/dotnet-skills
See how to install

Files included (4)

  • SKILL.md3.8 KB
  • manifest.json47 B
  • references/checklist.md6.5 KB
  • references/patterns.md17.2 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

.NET Code Review

Trigger On

  • reviewing a pull request or patch in a .NET repository
  • checking for behavioral regressions, API misuse, or missing tests
  • auditing architectural or framework-specific correctness

References

Workflow

  1. Prioritize correctness, data loss, concurrency, security, lifecycle, and platform-compatibility issues before style concerns. Use the checklist P0-P2 categories first.
  2. Check async flows, cancellation propagation, exception handling, disposal, and transient versus singleton lifetime mistakes. Refer to patterns.md for common pitfalls.
  3. Verify tests cover the changed behavior, not only the happy path or refactored implementation details.
  4. Inspect framework-specific boundaries such as EF query translation, ASP.NET middleware order, Blazor render state, or MAUI UI-thread access.
  5. Call out missing observability, migration risk, or runtime configuration drift when those are part of the change. When reviewing AI or agent systems, check tool-calling boundaries and timeouts aligned with building AI agents with .NET.
  6. Keep findings concrete, reproducible, and tied to specific files or behavior.

Key Review Patterns

Async Code

  • Async must propagate through the entire call chain; never use .Result, .Wait(), or .GetAwaiter().GetResult() in async contexts
  • Always propagate CancellationToken parameters
  • Use ConfigureAwait(false) in library code
  • Never use async void except for event handlers

Resource Disposal

  • Use using declarations or statements for all IDisposable resources
  • Use await using for IAsyncDisposable resources
  • Use IHttpClientFactory instead of creating HttpClient directly
  • Unsubscribe event handlers to prevent memory leaks
  • Validate DI service lifetimes to prevent captured dependencies

Security

  • Use parameterized queries or EF to prevent SQL injection
  • Validate all user input at system boundaries
  • Prevent path traversal by validating resolved paths stay within allowed directories
  • Never hardcode secrets; use configuration and secret management
  • Enforce authorization checks before accessing protected resources

Deliver

  • ranked review findings with file references
  • clear residual risks and test gaps
  • brief summary of what changed only after findings

Validate

  • findings describe user-visible or maintainability-impacting risk
  • assumptions are stated when repo context is incomplete
  • no trivial style nit hides a more serious issue

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

agentic-workflows

Free

Route gh-aw workflow design/create/debug/upgrade requests to the right prompts.

The English summary is being prepared. Showing the original description.

managedcode/dotnet-skills490Updated Oct 17, 2026

analyzer-config

Free

Use a repo-root `.editorconfig` to configure free .NET analyzer and style rules. Use when a .NET repo needs rule severity, code-style options, section layout, or analyzer ownership made explicit. USE FOR: the repo needs a root .editorconfig; analyzer severity and style ownership are unclear; the team wants one source of truth for rule configuration. DO NOT USE FOR: choosing analyzers with no config change; formatting-only execution with no config ownership question. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.

The English summary is being prepared. Showing the original description.

managedcode/dotnet-skills490Updated Oct 17, 2026

analyzing-dotnet-performance

Free

Scans .NET code for ~50 performance anti-patterns across async, memory, strings, collections, LINQ, regex, serialization, and I/O with tiered severity classification. Use when analyzing .NET code for optimization opportunities, reviewing hot paths, or auditing allocation-heavy patterns.

The English summary is being prepared. Showing the original description.

managedcode/dotnet-skills490Updated Oct 17, 2026

android-tombstone-symbolication

Free

Symbolicate the .NET runtime frames in an Android tombstone file. Extracts BuildIds and PC offsets from the native backtrace, downloads debug symbols from the Microsoft symbol server, and runs llvm-symbolizer to produce function names with source file and line numbers. USE FOR triaging a .NET MAUI or Mono Android app crash from a tombstone, resolving native backtrace frames in libmonosgen-2.0.so or libcoreclr.so to .NET runtime source code, or investigating SIGABRT, SIGSEGV, or other native signals originating from the .NET runtime on Android. DO NOT USE FOR pure Java/Kotlin crashes, managed .NET exceptions that are already captured in logcat, or iOS crash logs. INVOKES Symbolicate-Tombstone.ps1 script, llvm-symbolizer, Microsoft symbol server.

The English summary is being prepared. Showing the original description.

managedcode/dotnet-skills490Updated Oct 17, 2026

apple-crash-symbolication

Free

Symbolicate .NET runtime frames in Apple platform .ips crash logs (iOS, tvOS, Mac Catalyst, macOS). Extracts UUIDs and addresses from the native backtrace, locates dSYM debug symbols, and runs atos to produce function names with source file and line numbers. Automatically downloads .dwarf symbols from the Microsoft symbol server using Mach-O UUIDs. USE FOR triaging a .NET MAUI or Mono app crash from an .ips file on any Apple platform, resolving native backtrace frames in libcoreclr or libmonosgen-2.0 to .NET runtime source code, retrieving .ips crash logs from a connected iOS device or iPhone, or investigating EXC_CRASH, EXC_BAD_ACCESS, SIGABRT, or SIGSEGV originating from the .NET runtime. DO NOT USE FOR pure Swift/Objective-C crashes with no .NET components, or Android tombstone files. INVOKES Symbolicate-Crash.ps1 script, atos, dwarfdump, idevicecrashreport.

The English summary is being prepared. Showing the original description.

managedcode/dotnet-skills490Updated Oct 17, 2026

architecture

Free

Design or review .NET solution architecture across modular monoliths, clean architecture, vertical slices, microservices, DDD, CQRS, and cloud-native boundaries without over-engineering. USE FOR: .NET architecture choices; layer and domain boundary review; service decomposition; clean architecture, vertical slice, DDD, CQRS, and modular monolith decisions. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.

The English summary is being prepared. Showing the original description.

managedcode/dotnet-skills490Updated Oct 17, 2026

See all skills by managedcode

Report a problem with this skill