| name | build-check |
| description | Verify that all project services (API and Web) build successfully. Check compilation errors, type errors, and lint warnings. Use before running tests, before deployment, after code changes, and on resume. Trigger when build verification, compilation check, or pre-test validation is needed. |
Build Check
Verify builds succeed before proceeding with tests or deployment.
Build Commands
| Service | Source Build | Docker Build |
|---|
| API (.NET) | cd src/api && dotnet build | docker build -f src/api/Dockerfile . |
| Web (Next.js) | cd src/web && npm run build | docker build -f src/web/Dockerfile . |
Steps
- Identify services — Read
azure.yaml or scan src/ for service directories
- Build each service — Run the source build command for each service
- Capture errors — Collect compilation errors, type errors, and warnings
- Docker build (if preparing for deployment) — Run Docker build for each Dockerfile
- Report — Summarize build status per service
Output Format
Service: <name>
Status: PASS | FAIL
Errors: <count>
Warnings: <count>
Details:
- <file>:<line> <error message>
Notes
- Web (Next.js) requires
output: 'standalone' in next.config.ts
- API uses .NET 10 Minimal API
