dotnet-service-review

.NET Service Review

Conduct a full health review of this repository (or a subdirectory within it) by orchestrating four specialist agents.

Scope

This review is designed for microservice-sized repos (≤5 projects, ≤200 source files).

• Default: reviews the current working directory
• Subdirectory: pass a path to review a specific service within a larger repo (e.g., src/PaymentService)
• Large repos: the orchestrator will warn if the repo exceeds size thresholds and ask you to confirm or narrow scope

What Happens

1. Scope is validated (project/file count checked against thresholds)
2. SERVICE-REVIEW-CONTEXT.md is read from repo root if present (institutional knowledge)
3. Four agents launch in parallel on the scoped directory:
   • dotnet-architect — architecture, data flow diagram, integration points
   • dotnet-code-reviewer — code quality, .NET practices, security
   • dotnet-test-analyst — build, tests, testing trophy, maintainability
   • dotnet-modernization-analyst — migration complexity, runtime/deployment, modernization readiness
4. Results are collected and assembled into a single scored report (health score + separate modernization readiness score)
5. Report is written to SERVICE-REVIEW.md in the repo root

Recommended MCP Servers

MCP Server	Used By	What It Provides
GitNexus	dotnet-architect	Cross-repo dependency mapping, blast radius, integration context
RoslynMCP	dotnet-code-reviewer	Code metrics, compiler diagnostics, symbol analysis
Documentation (Confluence, Notion)	dotnet-architect	Wiki context for architectural decisions

All agents work without MCP servers — they enhance depth when available.

Also Available Individually

Run any agent standalone:

• /dotnet-service-review:architect — just the architecture analysis
• /dotnet-service-review:code-review — just the code review
• /dotnet-service-review:test-analysis — just the build/test analysis
• /dotnet-service-review:modernization-analysis — just the modernization readiness assessment