dotnet-claude-kit

Iteratively fix dotnet build errors. Runs an autonomous build-fix loop that parses compiler errors, categorizes them, applies fixes, and rebuilds until the build is green or the iteration limit is reached. Invoke when the build is broken, after a major refactor, after dependency updates, or when the user says "fix the build", "build is broken", "make it compile".

Save progress by creating a descriptive git commit and writing a handoff note. Use when the user wants to checkpoint work, save progress before a risky change, switch tasks, or pause for the day. Invoke when the user says "checkpoint", "save progress", "commit and handoff", "save state", "pause here".

MCP-powered multi-dimensional code review for .NET projects. Uses Roslyn analysis tools for antipatterns, diagnostics, references, and dependency graphs combined with structured manual review. Produces categorized findings with severity levels and actionable fix suggestions. Use when: "review", "code review", "PR review", "review this", "review my code", "check code quality", "review changes".

Systematic code cleanup pass. Triggers on: /de-sloppify, "clean this up", "cleanup pass", "tidy the code", "fix the mess", "before PR cleanup". Runs formatting, dead code removal, analyzer fixes, and structural improvements.

Interactive project initialization. Detects project type, asks architecture questions, and generates a customized CLAUDE.md — no manual template copying.

Minimal APIs, OpenAPI, versioning, rate limiting, and endpoint design for ASP.NET Core.

Autonomous build error fixing with iterative loops and contextual skill loading.

Multi-dimensional code review with architecture, security, and performance lenses.

Docker, CI/CD pipelines, Aspire orchestration, and deployment.

Architecture, project structure, module boundaries, and solution organization for .NET applications.

Focus code review effort on the 20% of code that causes 80% of issues. Prioritizes data access, security, concurrency, and integration boundaries over formatting and style. Uses blast radius scoring to determine review depth. Includes checkpoint schedules, critical path identification, and a batch review checklist. Load this skill when reviewing code, PRs, or architecture, or when the user mentions "review", "code review", "PR review", "what should I review", "review priorities", "blast radius", or "critical path".

API versioning strategies for ASP.NET Core. Covers Asp.Versioning library, URL segment, header, and query string strategies, version deprecation, and OpenAPI integration. Load this skill when adding versioning to an API, evolving an API with breaking changes, or when the user mentions "API version", "versioning", "v1/v2", "Asp.Versioning", "deprecation", "breaking change", or "backward compatibility".

Architecture selection advisor for .NET applications. Asks structured questions about domain complexity, team size, system lifetime, compliance, and integration needs, then recommends the best-fit architecture: Vertical Slice, Clean Architecture, DDD + Clean Architecture, or Modular Monolith. Load this skill when the user asks "which architecture", "choose architecture", "set up project", "new project", "architecture decision", "restructure", or "how should I organize". Always load BEFORE any architecture-specific skill.

.NET Aspire for cloud-native orchestration. Covers AppHost configuration, service defaults, resource configuration, service discovery, and the Aspire dashboard. Load this skill when setting up local development orchestration, service discovery, or Aspire-managed infrastructure, or when the user mentions "Aspire", "AppHost", "service defaults", "service discovery", "orchestration", "Aspire dashboard", "AddProject", "WithReference", or "cloud-native .NET".

Authentication and authorization for ASP.NET Core. Covers JWT bearer tokens, OpenID Connect, ASP.NET Identity, authorization policies, role and claim-based authorization, and API key authentication. Load this skill when implementing login, protecting endpoints, designing authorization rules, or when the user mentions "auth", "JWT", "bearer token", "OIDC", "OpenID Connect", "Identity", "claims", "roles", "authorize", "RequireAuthorization", "API key", or "cookie auth".

3 hooks across 2 events