菜单
Use when adding or changing a database model in this project. Covers the SQLModel table definition, the alembic autogenerate migration flow, and the query rules that keep access performant.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when cutting a release of the aegis-stack package. Covers the version-bump file set, the changelog cut, the three release gates, TestPyPI rc verification, and the tag-push mechanics that trigger the publish workflow.
Use when adding a new HTTP endpoint to this project's FastAPI backend. Covers the router module, request and response schemas, dependency wiring, router registration, the health surface, and the API test.
Use when adding a command to this project's own CLI (the app CLI under app/cli/, not the aegis tool). Covers the command module, Typer registration, the sync-plus-asyncio.run rule, and i18n strings.
Use when adding a job that runs on a schedule (periodic or at a fixed time) in this project. Covers writing the task function and registering it with the scheduler.
Use when adding or removing a capability (a component or service) in this project, or pulling framework updates. Covers the aegis add, remove, and update commands and what each one changes.
Use when an API endpoint in this project must require an authenticated user or a specific role. Covers the auth dependencies, attaching them to a route, and the session and cookie rules.
| name | add-model-and-migration |
| description | Use when adding or changing a database model in this project. Covers the SQLModel table definition, the alembic autogenerate migration flow, and the query rules that keep access performant. |
Database tables are SQLModel classes, and every schema change is captured by an alembic migration. The model and the migration are two separate artifacts: changing the model without generating a migration drifts the running schema from the code.
Use when adding a table, adding or changing a column, or adding an index.
Do NOT use for query-only changes that touch no schema (no migration needed), or for non-database state.
app/services/: models live in a service package as models.py (SQLModel
classes with table=True).alembic/env.py: imports the models so autogenerate can see them; a model it
cannot import is omitted from the migration.alembic/versions/: the generated revision lands here.models.py.alembic/env.py collects metadata, so
autogenerate sees it.alembic/versions/ and confirm it contains the intended change and nothing
spurious.make check: lint, typecheck, and test.WHERE id IN (...) or eager-load
relationships with selectinload() or joinedload(), or the query count
grows with the row count.alembic/env.py cannot import produces an empty or partial
migration, because autogenerate only sees imported metadata.