Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

Comenzar

backend-async-tasks

Estrellas2

Forks1

Actualizado17 de enero de 2026 a las 22:28

Use when creating or updating Celery tasks, async job logic, or Beat schedules in the backend.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

lmiguelvargasf

lmiguelvargasf/kerly

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas·SOC 15-1252

SKILL.md

readonly

name	backend-async-tasks
description	Use when creating or updating Celery tasks, async job logic, or Beat schedules in the backend.

Backend async tasks (Celery)

When to use

You are adding or changing a Celery task in backend/src/backend/apps/**/tasks.py.
You need to update the Celery Beat schedule in backend/src/backend/celery_app.py.
You are adding DB access inside a Celery worker process.

Steps

Define tasks only in a tasks.py file under the relevant app module.
Decorate tasks with @app.task imported from backend.celery_app.
Return a typed result (int, None, etc.). Keep task-specific parameters local unless they must be environment-configured.
For DB access:
- Use asyncio.run() to bridge async work.
- Always acquire a session via get_task_session() from backend.celery_app.
For periodic jobs, update app.conf.beat_schedule in backend/src/backend/celery_app.py and use celery.schedules.crontab.

Constraints and guardrails

Never use the global alchemy_config engine inside a task; it is not fork-safe for Celery workers.
Always use get_task_session() to manage DB connections safely across worker processes.

References

backend/src/backend/apps/**/tasks.py
backend/src/backend/celery_app.py
backend/tests/apps/users/test_tasks.py

Más de este repositorio

mismo repositorio

guardrails

lmiguelvargasf/kerly

Use for change discipline, validation expectations, and safety checks when making repo changes.

2026-02-072

workflow-taskfile

lmiguelvargasf/kerly

Use when running installs, dev servers, tests, lint/format, codegen, or Docker lifecycle tasks; Taskfile is the source of truth.

2026-02-072

sqlalchemy-code-review

lmiguelvargasf/kerly

Reviews SQLAlchemy code for session management, relationships, N+1 queries, and migration patterns. Use when reviewing SQLAlchemy 2.0 code, checking session lifecycle, relationship() usage, or Alembic migrations.

2026-01-222

web-design-guidelines

lmiguelvargasf/kerly

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".

2026-01-172

name	backend-async-tasks
description	Use when creating or updating Celery tasks, async job logic, or Beat schedules in the backend.

Backend async tasks (Celery)

When to use

You are adding or changing a Celery task in backend/src/backend/apps/**/tasks.py.
You need to update the Celery Beat schedule in backend/src/backend/celery_app.py.
You are adding DB access inside a Celery worker process.

Steps

Define tasks only in a tasks.py file under the relevant app module.
Decorate tasks with @app.task imported from backend.celery_app.
Return a typed result (int, None, etc.). Keep task-specific parameters local unless they must be environment-configured.
For DB access:
- Use asyncio.run() to bridge async work.
- Always acquire a session via get_task_session() from backend.celery_app.
For periodic jobs, update app.conf.beat_schedule in backend/src/backend/celery_app.py and use celery.schedules.crontab.

Constraints and guardrails

Never use the global alchemy_config engine inside a task; it is not fork-safe for Celery workers.
Always use get_task_session() to manage DB connections safely across worker processes.

References

backend/src/backend/apps/**/tasks.py
backend/src/backend/celery_app.py
backend/tests/apps/users/test_tasks.py