source-command-check

name	source-command-check
description	Run the canonical build plus all nine per-project test commands from docs/TESTING.md. Never uses solution-level dotnet test.

source-command-check

Use this skill when the user asks to run the migrated source command check.

Command Template

/check — Standard Verification Cycle

Source of truth: docs/TESTING.md “Test Projects” and “Run Commands”. AGENTS.md requires a Release build and individual project tests; this skill copies the exact nine canonical project commands.

When to Run

• Baseline — before any work, to confirm the repo is green.
• Post-edit — after every logical change unit, before marking a todo done.
• Pre-PR — before handing off to /review-pr.

The Commands (copy-paste, in this order)

1. Build (Release, quiet)

dotnet build --configuration Release --verbosity quiet

If exit code ≠ 0, STOP. Fix build errors before running tests.

2. Test Each Project Individually

dotnet test --project tests/Event.Domain.UnitTests/Event.Domain.UnitTests.csproj --configuration Release --verbosity quiet
dotnet test --project tests/Event.Application.UnitTests/Event.Application.UnitTests.csproj --configuration Release --verbosity quiet
dotnet test --project tests/Event.Architecture.Tests/Event.Architecture.Tests.csproj --configuration Release --verbosity quiet
dotnet test --project tests/Explore.Secrets.UnitTests/Explore.Secrets.UnitTests.csproj --configuration Release --verbosity quiet
dotnet test --project tests/Explore.Infrastructure.Tests/Explore.Infrastructure.Tests.csproj --configuration Release --verbosity quiet -- --treenode-filter "/*/*/*/*[Category!=Runtime]" --minimum-expected-tests 1
dotnet test --project tests/Event.Persistence.IntegrationTests/Event.Persistence.IntegrationTests.csproj --configuration Release --verbosity quiet
dotnet test --project tests/Event.API.IntegrationTests/Event.API.IntegrationTests.csproj --configuration Release --verbosity quiet
dotnet test --project tests/Explore.Blazor.IntegrationTests/Explore.Blazor.IntegrationTests.csproj --configuration Release --verbosity quiet
dotnet test --project tests/Explore.Blazor.Client.Tests/Explore.Blazor.Client.Tests.csproj --configuration Release --verbosity quiet

3. Scoped Run (intent-driven)

Prefer the intent's minimum_tests list over running everything. Example, for add-get-endpoint:

dotnet test --project tests/Event.API.IntegrationTests/Event.API.IntegrationTests.csproj --configuration Release --verbosity quiet
dotnet test --project tests/Event.Architecture.Tests/Event.Architecture.Tests.csproj --configuration Release --verbosity quiet

Run the full list only when the change touches multiple layers or you are about to open a PR.

Skipped by Default

On Failure

1. Generate a TRX for the failing project:

   dotnet test --project <ProjectPath> --configuration Release -- --report-trx --report-trx-filename results.trx
   

2. Fix failures before any planned work.
3. Do NOT delete or skip failing tests.
4. Report any failures that appear to be pre-existing (not caused by your change) separately — do not attempt to fix them without user direction.

Anti-Patterns

• ❌ Running dotnet test at the solution level. Always use --project.
• ❌ Running without --configuration Release. The repo's CI and architecture tests assume Release.
• ❌ Using findstr /i on French-locale Windows (unreliable).
• ❌ Modifying source to make a test pass rather than fixing the root cause.
• ❌ Running tests before the build is green.

Related

• docs/TESTING.md — canonical project list and command source.
• AGENTS.md — contribution and verification contract.
• docs/TROUBLESHOOTING.md — common failure modes.
• AGENTS.md — full cold-start workflow (includes this step).
• /review-pr — pre-PR checklist.