ワンクリックで
rulesgen-test-selection
Use for selecting the correct test, lint, type-check, or packaging command for a given Rulesgen change.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Use for selecting the correct test, lint, type-check, or packaging command for a given Rulesgen change.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
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-test-selection |
| description | Use for selecting the correct test, lint, type-check, or packaging command for a given Rulesgen change. |
| Change type | Command(s) |
|---|---|
Pure docs (README.md, NL-to-Python-*.md, docs/) | uv run ruff check . (skip pytest) |
Pydantic schema (src/rulesgen/schemas/**, domain/models.py) | uv run pytest tests/unit/test_<schema>.py, then uv run mypy src |
Compiler / parser / validator (src/rulesgen/compiler/**) | uv run pytest tests/unit/test_compiler.py tests/unit/test_runtime_properties.py |
Execution backend (src/rulesgen/execution/**) | uv run pytest tests/unit/test_opensandbox_runner.py tests/unit/test_opensandbox_backends.py tests/unit/test_generation_engine.py |
LLM gateway / cache (src/rulesgen/infra/**) | uv run pytest tests/unit/test_llm_gateway.py |
Services (src/rulesgen/services/**) | uv run pytest tests/unit/test_<service>_service.py |
FastAPI route (src/rulesgen/api/**, main.py) | uv run pytest tests/integration/test_api_flow.py tests/contract/test_problem_details.py |
Middleware (src/rulesgen/middleware/**) | uv run pytest tests/integration/ tests/contract/ |
Settings (src/rulesgen/core/config.py) | uv run pytest tests/unit/test_settings.py |
Library API (src/rulesgen/library.py) | uv run pytest tests/unit/test_library_api.py |
Auth (src/rulesgen/auth/**) | Add targeted unit tests; treat as medium-high risk |
Packaging (pyproject.toml, uv.lock) | uv lock --check && uv build |
CI (.github/workflows/**) | High-risk; escalate before changing |
uv run ruff check <touched paths> and uv run ruff format --check <touched paths>.uv run mypy src.uv run pytest (full suite) before opening a PR.Run the full suite: uv run pytest. It's fast enough that "I'm not sure which tests to run" is not a good reason to skip.