Use this skill to verify that a feature implementation is complete and correct. It enforces code style, compilation, and test passing.
Verification Steps
- •
Compilation
- •Run
dotnet buildin the root directory. - •Check: If the build fails, STOP. Report the errors using
read_fileto show the relevant code. - •Tip: For clean rebuild, use
/rebuild-clean
- •Run
- •
Code Formatting
- •Run
dotnet format --verify-no-changes. - •Check: If this fails, it means the code violates style rules.
- •Action: You can offer to fix it for the user by running
dotnet format(without --verify-no-changes).
- •Run
- •
Background Services Check
- •Ensure you are not running tests if the AppHost is already locking ports (if running locally).
- •Action: Stop any running
dotnetprocesses if needed.
// turbo 4. Run Tests (Unit & Integration)
- •Run
dotnet testto execute all test suites. - •Check: All tests must pass.
- •Action: If tests fail, analyze the results. Focus on any NEW failures related to the recent changes.
- •Granular Options:
- •
/run-unit-tests- Unit tests only - •
/run-integration-tests- Integration tests only
- •
- •Completion
- •If all steps pass, report: "✅ Feature verified: Builds, follows style guide, and passes all tests."
Related Skills
Typically Used After:
- •
/scaffold-write,/scaffold-read,/scaffold-frontend-feature- After implementing features - •
/scaffold-test- After creating tests - •
/debug-sse,/debug-cache- After fixing issues
Component Skills (for granular verification):
- •
/rebuild-clean- Clean build if compilation issues - •
/run-unit-tests- Run only unit tests - •
/run-integration-tests- Run only integration tests
See Also:
- •run-unit-tests - Unit test details
- •run-integration-tests - Integration test details
- •rebuild-clean - Clean build process
- •testing-guide - TUnit testing patterns
- •integration-testing-guide - Aspire testing