Menu
Use for release readiness, packaging, versioning, wheel, or dependency validation in Rulesgen.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
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.
| name | rulesgen-release-check |
| description | Use for release readiness, packaging, versioning, wheel, or dependency validation in Rulesgen. |
pyproject.toml:project.version is owned by python-semantic-release. Verify nobody hand-edited it on the release branch.feat: → minor, fix: → patch, ! / BREAKING CHANGE: → major; with major_on_zero = false and allow_zero_version = true while we're on 0.x).uv.lock is in sync: uv lock --check.uv build — should produce both dist/rulesgen-<version>-py3-none-any.whl and dist/rulesgen-<version>.tar.gz.uv run --no-sync python -m zipfile -l dist/rulesgen-*.whl — confirm no .env, .rulesgen-data/, ~.rulesgen-data/, developer config, or secrets are packaged. Use uv run so inspection runs in the project venv, not the system Python.cd "$(git rev-parse --show-toplevel)". Prefer --no-sync so the venv state is what CI will see:
uv run --no-sync ruff check .uv run --no-sync ruff format --check .uv run --no-sync mypy srcuv run --no-sync pytestuv run --no-sync pip-audit --skip-editable (triage HIGH/CRITICAL).
If any quality gate fails with ModuleNotFoundError, invoke rulesgen-bootstrap once and retry..github/workflows/ci.yml release job is unchanged outside approved scope. The release job:
main / master.secrets.DEPLOY_KEY SSH push.python-semantic-release@v10.2.0.v* tag.CHANGELOG.md updates only via semantic-release.A go/no-go checklist with each item marked pass/fail and evidence.
release job, DEPLOY_KEY usage, or [tool.semantic_release] config.pyproject.toml.uv publish from any non-CI environment.