debug:dotnet

Diagnose ASP.NET Core startup issues in DI, middleware, and configuration.

9|1|Updated Jan 12, 2026
One-click install
npx skills add https://github.com/SnakeO/claude-debug-and-refactor-skills-plugin --skill debug-dotnet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug:dotnet
Source: https://github.com/SnakeO/claude-debug-and-refactor-skills-plugin/tree/main/plugins/debug-and-refactor/skills/debug-dotnet
Command: npx skills add https://github.com/SnakeO/claude-debug-and-refactor-skills-plugin --skill debug-dotnet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a systematic approach to diagnosing and resolving ASP.NET Core startup issues, DI misconfigurations, middleware problems, and configuration binding failures, enabling faster remediation and stable deployments.

Core Features & Use Cases

  • DI & Startup Diagnostics: Detect missing registrations, circular dependencies, and lifetime misconfigurations in the dependency injection container.
  • Middleware & EF Core Troubleshooting: Analyze middleware order, routing, authentication flows, and common EF Core query performance issues.
  • Use Case: Imagine an app fails to start due to an unregistered service; this Skill guides you through a repeatable, four-phase debugging workflow to identify and fix root causes.

Quick Start

Use this skill to quickly identify DI, middleware, EF Core, and configuration binding issues in an ASP.NET Core project.

Frequently Asked Questions about debug:dotnet

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix ASP.NET Core startup failures caused by dependency injection misconfigurations?

ASP.NET Core startup failures are resolved by detecting missing registrations, circular dependencies, and lifetime mismatches using a systematic four-phase debugging workflow to identify and fix root causes.

What is the best way to troubleshoot EF Core query performance issues in ASP.NET Core?

Troubleshooting EF Core query performance issues involves analyzing middleware order and routing using Visual Studio, VS Code, and dotnet-trace to collect diagnostics and implement deterministic fixes across development and production environments.

How do I diagnose middleware ordering and configuration binding failures in ASP.NET Core?

Diagnosing middleware ordering and configuration binding failures requires analyzing the middleware pipeline using dotnet-dump and dotnet-counters to collect diagnostics and implement deterministic application fixes.

Can I use dotnet-trace and dotnet-dump to collect diagnostics for ASP.NET Core authentication workflows?

Yes, dotnet-trace and dotnet-dump collect diagnostics for ASP.NET Core authentication and authorization workflows across development and production environments to implement deterministic fixes.

Why does my ASP.NET Core app fail to start when a service is not registered in the DI container?

An ASP.NET Core app fails to start when services are unregistered in the DI container due to missing dependencies, requiring a repeatable debugging workflow to identify the registration gap and apply remediation.