build-test

Builds and tests .NET projects using PowerShell scripts with filtering and configuration options.

1|Updated Jan 26, 2026
One-click install
npx skills add https://github.com/miiitch/EzSCIM --skill build-test-miiitch
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: build-test
Source: https://github.com/miiitch/EzSCIM/tree/main/.github/skills/build-test
Command: npx skills add https://github.com/miiitch/EzSCIM --skill build-test-miiitch

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Manually running dotnet build and dotnet test commands with the right flags, filters, and configurations is repetitive and error-prone, especially when iterating on failing tests in a .NET solution. ## Core Features & Use Cases - Flexible Builds: Compile any project in the solution with Debug/Release configuration, optional clean, and verbosity control via build.ps1. - Filtered Test Runs: Execute tests by name pattern with configurable verbosity, no-build mode, and rebuild support via test.ps1. - Compilation Error Checking: Parse build output to list errors and warnings with file names and line numbers via check-errors.ps1. - Use Case: After modifying a PATCH handler in the EzSCIM integration tests, run a quick check for compilation errors, rebuild, and execute only the tests matching "Patch" to validate the change. ## Quick Start Ask the assistant to build the solution and run all tests matching the pattern "Patch" using the build-test skill.

Frequently Asked Questions about build-test

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

FAQPage Schema
How do I run only specific .NET tests by name?▼

Use the test script with the Filter parameter, which maps to dotnet test's FullyQualifiedName~ filter. For example, filtering with "Patch" runs only tests whose names contain that pattern.

How do I build a .NET project in Release configuration from PowerShell?▼

Run the build script with the Project and Configuration parameters. It locates the .csproj file recursively, optionally cleans first, and invokes dotnet build with the chosen configuration.

Can I run tests without rebuilding the project?▼

Yes, the test script supports a NoBuild switch that passes --no-build to dotnet test. This speeds up iteration when the code has not changed since the last build.

How do I check C# compilation errors without running tests?▼

Use the check script, which builds the project and parses the output for CS error and warning codes. It reports each issue with file name, line number, and message, and exits with code 1 if errors exist.

Why does the quick-test script fail on a different machine?▼

The quick-test and verify scripts contain a hardcoded absolute path to the project file from the original author's machine. Use the build and test scripts instead, which locate project files relative to the repository root.