What problem does it solve?
Reviewing a proposed public API for dotnet/aspnetcore requires deep knowledge of the @dotnet/aspnet-api-review team's unwritten conventions, and inconsistent reviews lead to permanent, hard-to-change public surface mistakes.
Core Features & Use Cases
- Need Assessment: Judges whether an API should exist at all by modeling real-world scenarios, commonality (happy-path vs edge-case), and target audience (end-app-developer vs library-author).
- Convention Enforcement: Applies ASP.NET Core-specific rules on naming, async/CancellationToken, nullability, return types, sealing, overloads, type placement, and breaking changes.
- Structured Output: Produces a verdict, per-type bullet changes with grounded reasoning, and a ref-assembly diff against the current repo API surface.
- Use Case: Given an api-ready-for-review issue proposing a new endpoint helper, the Skill evaluates whether it belongs in the framework, flags a missing CancellationToken and an unsealed class, and emits a diff showing the recommended signature.
Quick Start
Ask the AI to review this ASP.NET Core API proposal and recommend changes to its public shape.