cck-verify

Verify .NET solution builds, tests, formatting, and git status before commits.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures the repository compiles, all tests pass, and code formatting is correct before commits or pull requests, preventing broken builds, failing tests, and accidental style or migration changes from entering shared branches.

Core Features & Use Cases

  • Restore and Build: Run dotnet restore and dotnet build in Release configuration to confirm successful compilation.
  • Run Tests: Execute all tests or targeted test projects and individual test filters to ensure zero test failures.
  • Format Verification: Verify formatting using dotnet format --verify-no-changes and guide developers to run dotnet format if issues are found.
  • Git Status Check: Inspect git status to catch unintended changes to configuration, environment files, migrations, or binaries before committing.
  • Use Cases: Run before every git commit, before opening a PR, after merging from main, after adding NuGet packages, or after creating EF Core migrations.

Quick Start

Run the verification sequence: restore and build the solution, run all tests, verify formatting, and check git status before creating a pull request.

Frequently Asked Questions about cck-verify

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

FAQPage Schema
How do I verify my .NET project builds and tests pass before a git commit?

To verify a .NET project before a commit, run dotnet restore and dotnet build in Release configuration, execute dotnet test to ensure zero failures, and check git status to confirm only intended files are modified.

What is the best way to enforce dotnet formatting checks before a pull request?

Enforcing dotnet formatting before a pull request involves running dotnet format --verify-no-changes to detect style violations. If formatting issues are found, developers should run dotnet format to correct the code style automatically.

How do I prevent accidental EF Core migration changes from being committed in git?

Preventing accidental migration changes in git requires inspecting git status before committing. This check catches unintended modifications to configuration, environment files, EF Core migrations, or binaries before they enter shared branches.

Can I run specific unit test filters during my .NET pre-commit validation?

Yes, you can run specific unit test filters during .NET pre-commit validation. The verification process supports executing all tests or targeting individual test projects and filters to ensure zero test failures before proceeding.

Does dotnet format --verify-no-changes fail the build if code style is incorrect?

Yes, dotnet format --verify-no-changes identifies formatting violations without altering files. When formatting issues are detected during verification, the process flags them and guides developers to run dotnet format to resolve the errors.

When should I run dotnet restore and build after adding a NuGet package?

After adding a NuGet package, you should run dotnet restore and dotnet build to confirm successful compilation. Running this verification sequence ensures the new dependency integrates correctly without breaking the existing solution.