verify-feature

Verifying a dotnet feature branch requires running build, format, and test checks to ensure a Definition of Done is met. This skill automates that verification pipeline by invoking dotnet build, dotnet format --verify-no-changes, and dotnet test in the repository root to confirm feature readiness.

A Definition of Done pipeline for dotnet features ensures code compiles, conforms to formatting style, and passes all tests. This skill provides a deterministic verification process by running dotnet build, format verification, and test execution to reduce regression risk before merging.

Yes, you can use this verification process in CI pipelines to ensure deterministic feature checks. It applies to feature development and CI pipelines by running build, format verification, and test commands in the repository root to enforce a reproducible Definition of Done.

Yes, you need dotnet tooling available in your environment to run format and test checks. The skill requires the dotnet CLI to execute build, format verification, and test commands directly in the repository root directory.

The best way to automate dotnet format verification is to include it in a deterministic pipeline alongside build and test steps. This skill runs dotnet format --verify-no-changes to check style conformance without modifying files, ensuring code meets formatting standards before merging.

Your dotnet build may pass but format verification fails when code style does not conform to formatting rules. This skill runs dotnet format --verify-no-changes to detect style violations, ensuring code is properly formatted before the feature is considered complete.