القائمة
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.
التثبيت باستخدام 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 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.
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-scheduled-job |
| description | 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. |
Scheduled work runs under the scheduler component. Jobs are registered
explicitly in the scheduler entry point by importing a function and calling
scheduler.add_job(...), so a schedule is not active until the job is
registered there.
Use when work must run periodically or at a fixed time (a cron-like schedule).
Do NOT use for work triggered by a request (see the add-background-job skill
if a worker is present, or add-api-endpoint for a synchronous route).
app/components/scheduler/main.py: the scheduler entry point; import the task
function and register it with scheduler.add_job(...) and a trigger.app/components/scheduler/main.py, import the function and register it
with scheduler.add_job(...), giving it an interval or a fixed-time trigger.make check: lint, typecheck, and test.scheduler.add_job(...) never
runs; registration in the entry point is what activates the schedule.