api-review Skill
Reviews .NET API surface area PRs for design guideline violations. Analyzes api/.cs file diffs, applies review rules from .NET Framework Design Guidelines and Aspire conventions, and attributes findings to the developer who introduced each API (via git blame). Use this when asked to review API surface area changes. Published by microsoft in aspire.
Decision snapshot
Is this a fit?
Design and media, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
2 months ago · MIT license
No specific cautions were detected. Review the source and requested permissions before installing.
What is api-review Skill?
Reviews .NET API surface area PRs for design guideline violations. Analyzes api/.cs file diffs, applies review rules from .NET Framework Design Guidelines and Aspire conventions, and attributes findings to the developer who introduced each API (via git blame). Use this when asked to review API surface area changes. Published by microsoft in aspire. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Design and media
- Design and media use cases
Declared skill metadata
- Source file: .agents/skills/api-review/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use api-review Skill
- Use it for design and media.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/aspire
- Skill file: .agents/skills/api-review/SKILL.md
What it does
Reviews .NET API surface area PRs for design guideline violations. Analyzes api/.cs file diffs, applies review rules from .NET Framework Design Guidelines and Aspire conventions, and attributes findings to the developer who introduced each API (via git blame). Use this when asked to review API surface area changes.
Skill instructions
You are a .NET API review specialist for the dotnet/aspire repository. Your goal is to review API surface area PRs — the auto-generated api/.cs files that track the public API — and identify design guideline violations, inconsistencies, and concerns. Background Aspire uses auto-generated API files at src//api/.cs and src/Components//api/.cs to track the public API surface. A long-running PR (branch update-api-diffs) is updated nightly with the current state of these files so the team can review the running diff of new APIs before each release. This skill reviews those PRs. The API files contain method/property signatures with throw null bodies, organized by namespace. Example: csharp namespace Aspire.Hosting { public static partial class ResourceBuilderExtensions { public static IResourceBuilder<T WithEndpoint<T(this IResourceBuilder<T builder, int? port = null) where T : IResourceWithEndpoints { throw null; } } } Task Execution Steps Step 1: Get the PR Diff Get the diff of API files f
Verified compatibility and discovery
Frequently asked questions
What is api-review?
api-review is a open-source AI agent skill with Copy skill directory. Reviews .NET API surface area PRs for design guideline violations. Analyzes api/.cs file diffs, applies review rules from .NET Framework Design Guidelines and Aspire conventions, and attributes findings to.
Who is api-review best for?
api-review is best for reusing agent instructions, scripts, and references, design and media workflows.
How do I install api-review?
Install or run api-review using Copy skill directory. Check api-review for the latest setup command.
Is api-review actively maintained?
api-review may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
