cck-build-fix

Diagnose and fix .NET build, test, and formatting failures.

2|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/s205109/AHKFlowApp --skill cck-build-fix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cck-build-fix
Source: https://github.com/s205109/AHKFlowApp/tree/main/.claude/skills/cck-build-fix
Command: npx skills add https://github.com/s205109/AHKFlowApp --skill cck-build-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers diagnose and resolve build failures, failing tests, EF Core migration issues, and formatting/lint violations so the repository returns to a healthy, buildable state.

Core Features & Use Cases

  • Error triage: Read and interpret full dotnet build and test outputs to identify compiler error codes, file paths, and root causes.
  • Dependency and namespace fixes: Detect missing package references, incorrect usings, and namespace mismatches and recommend project or NuGet changes.
  • Configuration and runtime guidance: Advise on EF Core migration setup, startup project selection, Docker/Testcontainers prerequisites, and formatting enforcement.
  • Use Case: When CI reports a broken build due to CS0246 or failing integration tests because Docker is not running, use this Skill to locate the failure, suggest concrete code or project-file fixes, and verify formatting and migrations.

Quick Start

Run dotnet build --configuration Release and paste the full error output here so I can diagnose and propose fixes.

Frequently Asked Questions about cck-build-fix

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

FAQPage Schema
How do I fix dotnet build failures caused by missing package references and namespace mismatches?

Diagnose dotnet build failures by reading compiler error outputs to locate missing type definitions, correcting incorrect usings, and updating project or NuGet package references to resolve namespace mismatches.

Why do my .NET integration tests fail with Testcontainers when Docker is not running?

.NET integration tests fail with Testcontainers because Docker is a required runtime prerequisite; you must start the Docker daemon before running the tests to allow the containerized test dependencies to initialize properly.

How do I resolve EF Core migration failures in a .NET 10 application?

Resolve EF Core migration failures by verifying the correct startup project selection, applying pending database context updates, and running migration commands to ensure the schema changes execute successfully.

Can this Skill diagnose and fix formatting violations in my .NET project?

Yes, the Skill can diagnose and fix formatting violations by running formatting checks against your .NET project and recommending the necessary code style corrections to return the repository to a compliant state.

What's the best way to troubleshoot failing unit tests and compiler errors in a .NET repository?

The best way to troubleshoot failing unit tests and compiler errors is to run dotnet build --configuration Release, paste the full error output for analysis, and apply the suggested code or project-file fixes to restore the build.

Do I need Docker installed to fix .NET test failures with this Skill?

Yes, you need Docker installed and running because the Skill enforces Docker as a prerequisite for Testcontainers, which are used to execute integration tests that depend on containerized environments.