Menu
Generate Alembic database migrations using GitHub Actions. Use when user asks to generate or autogenerate a migration.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Project conventions for writing pytest tests in aaiclick — file layout, flat structure, async test rules, what NOT to test, Object API alignment. TRIGGER when creating or editing `test_*.py` files, `conftest.py`, or when asked to write/review tests.
Project markdown style rules — heading style, table formatting, admonitions, implementation references. TRIGGER when writing or editing `.md` files in subdirectories (`docs/`, `aaiclick/**`). Skip root-level `.md` files (`CLAUDE.md`, `README.md`, `CHANGELOG.md`).
| name | generate-migration |
| description | Generate Alembic database migrations using GitHub Actions. Use when user asks to generate or autogenerate a migration. |
Trigger a GitHub Actions workflow to autogenerate Alembic migrations.
gh workflow run generate-migration.yaml -f message="your migration description"
Then monitor:
# Get run ID
RUN_ID=$(gh run list --workflow=generate-migration.yaml --limit 1 --json databaseId --jq '.[0].databaseId')
# Watch it
gh run watch $RUN_ID
The workflow:
alembic revision --autogenerategit pullgh run view <run-id> --log