メニュー
Run backend pytest with the right venv automatically. Optionally pass a path or test name to filter. Use when the user says "run tests", "test X", or after making changes that need verification.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | test |
| description | Run backend pytest with the right venv automatically. Optionally pass a path or test name to filter. Use when the user says "run tests", "test X", or after making changes that need verification. |
The constant trip-up: the backend venv is at backend/.venv (not repo root). Activating from the wrong place silently uses the system interpreter and either errors on missing deps or — worse — runs against an outdated environment. This skill encodes the right invocation.
The skill takes an optional argument:
/test (no arg) → run everything: cd backend && uv run pytest -q/test tests/unit/domain/agents/ → run a directory/test tests/unit/infrastructure/cli_launcher/test_build_resume_command.py::test_amp_includes_mode_flag → run a single test by node id/test -k "ctx_pct" → pass through pytest's -k filterPass the argument straight to pytest after the path setup. Don't try to be clever about parsing; pytest's CLI handles it.
cd backend && uv run pytest <args>
uv run activates the venv on the fly — faster than source .venv/bin/activate && python -m pytest and avoids polluting the user's shell. It also picks the right interpreter every time, even if the user has a different one on PATH.
If the user prefers verbose output or a specific format, pass through their preference. The default is -q (quiet) since most runs the user wants the pass count + any failures, not the full collection list.
If pytest exits non-zero:
pytest --tb=short already does this; don't post-process.-x -vv for more detail.If everything passed, surface the count + duration. One line: 720 passed in 11.94s.
This skill is backend-only by default. If the user asks for "frontend tests" or "all tests", run:
cd frontend && npm test
Frontend test infra is conventional Vitest — no special venv handling needed.
tsc (frontend) or mypy (backend). Could be a separate /typecheck skill if it ever becomes worth it.ruff / eslint) — same.Pull latest main, install dependencies, run any pending FS-side migrations, and remind the user to restart dev. Use when the user says "update", "pull latest", or "sync with main".
Start the Atelier dev servers (backend on 8001, frontend on 4173). Wraps scripts/dev.sh, scripts/dev-backend.sh, scripts/dev-frontend.sh. Use when the user wants to start, restart, or boot the local dev environment.
Run all pending FS-side state migrations. Use after pulling changes that may have rewritten on-disk shapes (transcripts, work.json, agent.json). Called by /update and runnable directly. Does NOT run DB schema migrations — those auto-apply on backend boot.
Scaffold a new migration. Two flavours — db (a step in backend/src/infrastructure/database/migrations.py) or fs (a new scripts/migrate-<slug>.py). Use when changing a SQL schema, transcript shape, or any on-disk JSON shape. Invoke as /new-migration db <slug> or /new-migration fs <slug>.
Destructive cleanup of Atelier state — wraps scripts/wipe.sh. Use only when the user explicitly asks to wipe, reset, or start fresh. Requires the backend to be stopped first.