菜单
Verify Alembic schema migrations locally against a throwaway PostgreSQL — full upgrade chain incl. seeds, model↔migration drift via alembic check, and a downgrade/upgrade roundtrip — without ever touching the shared Cloud SQL DB. Use when asked to verify, test, or check a migration, a schema change, or alembic revisions before pushing.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Work off the Werkbank's Auftragskorb (the work_items basket) — read the open tasks, reproduce each complaint, restate it back into the row, triage it along the stage doctrine, fix the RULE rather than one spot, measure the effect and close the item with the diagnosed stage. Use when asked to work off the Korb, handle work items, process filed optimization tasks, or start an optimization round.
Take a finished change from diff to an open, green, review-clean PR — run the matching verify skills and the local CI gates first, then commit, push and open the PR, watch the pipeline AND the Copilot review, fix sensible findings and resolve the review threads. Never merges unless the user explicitly asks in this session. Use when asked to open or create a PR, ship a change, or finish up a change.
Run and exercise the FastAPI backend — start uvicorn, sweep the read endpoints with curl, check the diagnostic/fit/crop payloads against the live DB, and probe the admin write gate. Use when asked to run, start, test, or verify the API, a router, an endpoint, or a backend change.
Test and smoke-run the pure-Python compute layer in core/ — run pytest, run ruff lint/format the way CI does, and call the extraction pipeline directly on a synthetic chart without DB or HTTP. Use when asked to run, test, lint, or verify core/, the pipeline, extraction, template, or fit code.
Run and visually verify the kurrentschrift app after frontend changes — start the dev servers, click through ONLY the flows the change touches (chrome-devtools MCP locally, or playwright-core against the pre-installed Chromium in the cloud), watch the console and network, check style fidelity and legibility at a desktop AND a mobile viewport, and record a performance trace when the change can move performance. Use when asked to run, start, screenshot, verify, test in the browser, or visually check the app or a frontend change.
Conventions and checklist for writing or updating the internal design docs under docs/ — German language rules, where a new doc goes, keeping docs/index.md and the CLAUDE.md/copilot-instructions pair in sync, and what is settled (verworfen) and must not be re-litigated. Use when asked to write, add, update, or restructure documentation, concepts, or reference docs.
| name | verify-migrations |
| description | Verify Alembic schema migrations locally against a throwaway PostgreSQL — full upgrade chain incl. seeds, model↔migration drift via alembic check, and a downgrade/upgrade roundtrip — without ever touching the shared Cloud SQL DB. Use when asked to verify, test, or check a migration, a schema change, or alembic revisions before pushing. |
The shared Cloud SQL DB must never see an untested revision. This skill
runs the exact sequence the CI migrations job runs
(.github/workflows/ci.yml), locally, against a disposable PostgreSQL —
so a broken revision, a model↔migration drift or a missing downgrade is
caught before the push.
With Docker (local machine):
docker run --rm -d --name pg-migrate-check -e POSTGRES_USER=postgres \
-e POSTGRES_PASSWORD=postgres -e POSTGRES_DB=kurrentschrift -p 55432:5432 postgres:16
Without Docker (Claude Code web container — Postgres 16 is installed,
but initdb refuses root, so run it as an unprivileged user under
/var/tmp; the scratchpad mount denies other users):
useradd -m pguser 2>/dev/null; mkdir -p /var/tmp/pgscratch && chown -R pguser /var/tmp/pgscratch
su pguser -c "/usr/lib/postgresql/16/bin/initdb -D /var/tmp/pgscratch/data -U postgres --auth=trust -E UTF8 >/dev/null \
&& /usr/lib/postgresql/16/bin/pg_ctl -D /var/tmp/pgscratch/data -o '-p 55432 -k /var/tmp/pgscratch' -l /var/tmp/pgscratch/pg.log start \
&& /usr/lib/postgresql/16/bin/createdb -h /var/tmp/pgscratch -p 55432 -U postgres kurrentschrift"
export DATABASE_URL='postgresql+asyncpg://postgres:postgres@localhost:55432/kurrentschrift'
uv run alembic upgrade head # full chain incl. seeds
uv run alembic check # model ↔ migration drift (autogenerate diff)
uv run alembic downgrade -1 && uv run alembic upgrade head # newest revision reversible
Expected: upgrade ends at head; check prints "No new upgrade operations detected."; the roundtrip runs both directions without error.
docker rm -f pg-migrate-check # docker variant
su pguser -c "/usr/lib/postgresql/16/bin/pg_ctl -D /var/tmp/pgscratch/data stop" && rm -rf /var/tmp/pgscratch # container variant
Unset DATABASE_URL (or close the shell) afterwards so no later
command accidentally runs against the throwaway URL — or worse, so you
don't forget it and export the shared .env URL into an alembic call.
alembic check needs the DB already migrated to head — run it
after upgrade head, never against an empty DB (everything would
look like drift).modify_nullable finding is usually a forgotten
nullable=False in a revision, not a model bug — 0004 declares it
on every created_at; new tables must too (0010 forgot it once,
fixed by 0013)./verify-api (user=kurrentschrift db=kurrentschrift means SHARED)
applies to every alembic command; this skill exists precisely so the
shared instance never runs experimental DDL.kurrentschrift-migrate
Cloud Run job in the deploy pipeline (api/cloudbuild.yaml), never
ad-hoc DDL.