Menu
Use for GitHub Actions CI failures (ruff, mypy, pytest, uv build, pip-audit, semantic-release) in Rulesgen.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | rulesgen-ci-triage |
| description | Use for GitHub Actions CI failures (ruff, mypy, pytest, uv build, pip-audit, semantic-release) in Rulesgen. |
.github/workflows/ci.yml:
uv sync --extra api --extra dev --locked → lockfile drift, dependency resolution.uv run ruff check . / uv run ruff format --check . → lint or formatting.uv run mypy src → strict typing.uv run pytest → unit / integration / contract test failure.uv build → packaging.uv run pip-audit → vulnerability finding (non-blocking, continue-on-error: true, but triage anyway).release job → python-semantic-release failure (escalate, do not retry blindly).pyproject.toml changed but uv.lock did not (or vice versa).uv lock --check. The harness denies bare uv lock (would mutate the lockfile without review).APPROVAL REQUIRED: regenerate uv.lock for <change description> and wait for approved per CLAUDE.md "Approval contract". After approval, run uv lock then commit both files.uv run ruff check . --fix and uv run ruff format . for safe auto-fixes.Any generics.# type: ignore without a comment naming the specific reason.uv run pytest tests/<path>::<test> -q -x.uv build failures:
pyproject.toml or a missing src/rulesgen/__init__.py field.pip-audit findings:
uv add 'pkg>=X.Y' and update uv.lock.main to "see if CI passes."release job manually.--locked by deleting uv.lock.uv lock or uv sync — both denied by the harness for safety. Use uv lock --check and uv sync --locked (or escalate).--no-verify) — .pre-commit-config.yaml mirrors CI.Use when adding, renaming, reordering, or linking Rulesgen public docs that flow to the tdm-docs Docusaurus site and tdspora.ai. Covers the import pipeline, sidebar/.order mechanics, the "link locally until published" rule, and the lychee link-check and docs-contract validation battery.
Use for authoring or updating Rulesgen documentation — public docs (`docs/public/`), repo-root design docs, contributor docs, sample READMEs, and the glossary. Produces testable, glossary-aligned, link-integral docs.
Use for testing Rulesgen documentation — executes Markdown code fences via Sybil, validates link integrity, lints glossary usage, and cross-checks docs against Settings, schemas, and routes.
Use for authoring, reviewing, or correcting natural-language → Python generation DSL rules for Rulesgen.
Use for implementing production-grade Rulesgen features or non-trivial code changes.
Use for Pydantic v2 validation errors, DSL parser/validator rejections, and API request validation issues in Rulesgen.