菜单
Run the canonical build plus all nine per-project test commands from docs/TESTING.md. Never uses solution-level dotnet test.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Create or re-baseline lean, repository-grounded implementation plans and persistent dev docs when users ask for an implementation plan, technical plan, feature plan, refactor plan, or dev-docs workstream.
Senior CTO review workflow for repository-grounded implementation-plan workstreams used before coding.
Apply project EF Core conventions for repositories, DbContext setup, query filters, migrations, and seeded lookup data.
Create a self-contained HTML artifact focused on a high-quality SVG architecture or system diagram with minimal supporting prose.
Create a pragmatic self-contained HTML plan that organizes the user's plan content visually without expanding the scope unnecessarily.
Create a self-contained HTML artifact for reports, explainers, comparisons, prototypes, or decks when no narrower HTML diagram or plan skill applies.
| 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. |
Use this skill when the user asks to run the migrated source command check.
Source of truth:
docs/TESTING.md“Test Projects” and “Run Commands”.AGENTS.mdrequires a Release build and individual project tests; this skill copies the exact nine canonical project commands.
/review-pr.dotnet build --configuration Release --verbosity quiet
If exit code ≠ 0, STOP. Fix build errors before running tests.
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
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.
dotnet test --project <ProjectPath> --configuration Release -- --report-trx --report-trx-filename results.trx
dotnet test at the solution level. Always use --project.--configuration Release. The repo's CI and architecture tests assume Release.findstr /i on French-locale Windows (unreliable).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.