autojudge-api-changes

name	autojudge-api-changes
description	Use when adding or modifying AutoJudge API routes, model classes, auth checks, MySQL-backed entity behavior, or API Jest coverage. Covers the route-model-helper-test workflow used in api/.
user-invocable	true
argument-hint	API route, model, or auth change to implement or review

AutoJudge API Changes

Use this skill for backend work in api/.

What To Inspect First

1. The mounted route in api/app.js.
2. The owning route file in api/route/.
3. The matching model class in api/model/.
4. The nearest unit or integration test in api/tests/.

Workflow

1. Keep transport logic in the route and persistence or relation logic in the model.
2. Reuse CustomError and existing auth middleware before introducing new status or auth patterns.
3. Preserve the current JSON response style with a message field and explicit status codes.
4. Update the narrowest existing Jest coverage that proves the changed behavior.
5. Validate with cd api && npx jest --config jest.unit.config.mjs or cd api && NODE_ENV=test npx jest --config jest.integration.config.mjs, depending on the changed slice.

Notes

• Integration tests depend on MySQL and NODE_ENV=test semantics.
• If a change needs Compose networking or service DNS names, validate in Docker or state that the check was not runnable.
• Use AGENTS.md for shared repo commands and environment constraints.