| name | autojudge-validation |
| description | Use when validating AutoJudge API, web, judge, background, or Docker Compose changes. Covers the narrowest honest command selection for Jest, Webpack rebuilds, and container-aware checks. |
| user-invocable | true |
| argument-hint | Changed area and behavior that needs validation |
AutoJudge Validation
Use this skill whenever work in this repo changes behavior.
Choose The Narrowest Validation
- API unit-only logic:
cd api && npx jest --config jest.unit.config.mjs
- API behavior with MySQL or route integration:
cd api && NODE_ENV=test npx jest --config jest.integration.config.mjs
- Web source changes that ship assets:
cd web && npx webpack --mode production
- Compose-only behavior: validate against the running stack started with
docker compose -f compose.local.yaml up -d --build when possible.
Workflow
- Pick the smallest command that can falsify the change.
- Run that command before widening scope.
- If the change touches Docker DNS, judge execution, background polling, or PDF generation, note whether container-backed validation was available.
- Finish by stating what was run, what was not run, and any environment blockers.
Notes
- Integration tests need MySQL access and may be easiest to run inside the API container.
- Judge and background changes often require the full Compose stack because they depend on container networking and the Docker socket.
- Use
AGENTS.md for the shared service map and command list.