Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

sched-uv-workflow

Sterne4

Forks1

Aktualisiert22. März 2026 um 23:05

Develops and runs the course-constraint-scheduler package with uv. Use when installing dependencies, syncing the lockfile, running CLI/server modules, or setting up a local environment for this repository.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

mucsci

mucsci/Scheduler

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

Netzwerk- und ComputersystemadministratorenInformatik- und Mathematikberufe·SOC 15-1244

SKILL.md

readonly

name	sched-uv-workflow
description	Develops and runs the course-constraint-scheduler package with uv. Use when installing dependencies, syncing the lockfile, running CLI/server modules, or setting up a local environment for this repository.

UV workflow (this repo)

Defaults

Python: 3.12+ (requires-python in pyproject.toml).
Package: course-constraint-scheduler; code under src/scheduler/, import scheduler.
Lockfile: uv.lock — prefer uv sync --locked in CI-like checks.

Setup

uv sync

Dev tools (ruff, pytest, ty, prek, …) are in the dev dependency group; tool.uv.default-groups includes dev, so plain uv sync is enough for normal work.

Run entrypoints

uv run python -m scheduler.main --help
uv run python -m scheduler.server --help
uv run pytest
uv run prek run --all-files

Use uv run <command> so the project venv and paths stay consistent.

For CI parity and GitHub Actions behavior, see sched-github-ci.

Mehr aus diesem Repository

gleiches Repository

sched-cli-main

mucsci/Scheduler

Changes the scheduler command-line interface in main.py (Click), arguments, output paths, and format options. Use when adding CLI flags or adjusting how schedules are printed or written to disk.

2026-03-224

sched-domain-z3-config

mucsci/Scheduler

Implements or debugs scheduling logic, Z3 constraints, and JSON configuration for the course constraint scheduler. Use when working in scheduler.py, config models, time slots, or solver behavior.

2026-03-224

sched-fastapi-server

mucsci/Scheduler

Changes or reviews the FastAPI REST server, routes, and HTTP behavior for the scheduler. Use when editing server.py, async job flow, or API contracts.

2026-03-224

sched-fern-openapi-docs

mucsci/Scheduler

Maintains Fern documentation, OpenAPI, JSON Schema assets, and Python API reference MDX for this project. Use when changing FastAPI routes, public docstrings, Pydantic config models, or user-facing docs under fern/docs.

2026-03-224

sched-github-ci

mucsci/Scheduler

Interprets or updates GitHub Actions workflows for linting, tests, docs, and publishing. Use when CI fails, when adding checks, or when aligning local commands with automation.

2026-03-224

sched-json-types

mucsci/Scheduler

Maintains TypedDict and JSON-shaped type definitions for API and config payloads. Use when editing json_types.py or aligning wire formats with Pydantic models and OpenAPI.

2026-03-224

name	sched-uv-workflow
description	Develops and runs the course-constraint-scheduler package with uv. Use when installing dependencies, syncing the lockfile, running CLI/server modules, or setting up a local environment for this repository.

UV workflow (this repo)

Defaults

Python: 3.12+ (requires-python in pyproject.toml).
Package: course-constraint-scheduler; code under src/scheduler/, import scheduler.
Lockfile: uv.lock — prefer uv sync --locked in CI-like checks.

Setup

uv sync

Dev tools (ruff, pytest, ty, prek, …) are in the dev dependency group; tool.uv.default-groups includes dev, so plain uv sync is enough for normal work.

Run entrypoints

uv run python -m scheduler.main --help
uv run python -m scheduler.server --help
uv run pytest
uv run prek run --all-files

Use uv run <command> so the project venv and paths stay consistent.

For CI parity and GitHub Actions behavior, see sched-github-ci.