Menú
Apply when changing the REST API surface — actix handlers, utoipa annotations, or request/response types under server/.
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.
Basado en la clasificación ocupacional SOC
Apply for build/test/lint, dependency or feature changes, and editing Cargo.toml or .cargo config in this repo.
Apply when starting work, branching, committing, opening/reading PRs, reading issues, or checking CI — the git + GitHub (gh) workflow.
Apply when creating or tracking a GitHub issue, or planning multi-step work — the issue template and the task convergence loop.
Apply when writing, editing, reviewing, or refactoring ANY code in this repo — coding-behavior rules to avoid overcomplication and make surgical, verifiable changes.
Apply when editing .proto files or the generated protobuf types (src/pbs/*) in this repo.
Apply when working in mehari-python/ — the PyO3/maturin Python extension.
| name | openapi |
| description | Apply when changing the REST API surface — actix handlers, utoipa annotations, or request/response types under server/. |
server feature. ApiDoc in mehari/src/server/run/mod.rs; Swagger UI via utoipa-swagger-ui.openapi.schema.yaml (repo root). A CI Schema job regenerates it and diffs against the committed file (stripping the version: line), so it must stay in sync.After ANY API-surface change (routes, handlers, #[utoipa::path], schema structs), regenerate and commit the schema in the same PR, or CI fails:
cargo run -p mehari --bin mehari -- server schema --output-file openapi.schema.yaml
Review the diff (the version: line doesn't matter — CI strips it).