一键在 Manus 中运行任何 Skill

开始使用

rulesgen-validation-debugging

星标0

分支0

更新时间2026年5月28日 09:05

Use for Pydantic v2 validation errors, DSL parser/validator rejections, and API request validation issues in Rulesgen.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

tdspora

tdspora/tdm_rulesgen

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Rulesgen Validation Debugging

Workflow

Capture the exact failing input (request body, DSL text, or library call) and the full error message.
Classify the failure:
- Pydantic schema — ValidationError raised in rulesgen/schemas/* or rulesgen/domain/models.py. Locate the offending field via the error loc tuple.
- DSL parser — failure in rulesgen/compiler/parser.py. Reproduce with a minimal DSL snippet and a unit test in tests/unit/test_compiler.py.
- DSL validator — AST rejected by rulesgen/compiler/validator.py. Check whether the rejection is expected for safety; if so, document why; if not, narrow the validator rule.
- Runtime properties — type or shape mismatch in RuntimeSpec. Check rulesgen/compiler/runtime_spec.py and tests/unit/test_runtime_properties.py.
- API request validation — FastAPI rejected the request before the route. Look at the route signature, the dependency in rulesgen/api/dependencies.py, and the schema in rulesgen/schemas/.
Confirm the contract:
- For schema changes: are positive and negative tests present?
- For DSL changes: does requirements/NL-to-Python-Generation-DSL.md describe this form?
- For API changes: does the error surface as RFC 7807 Problem Details (tests/contract/)?
Write or update a failing test that reproduces the bug before changing production code.
Fix in the smallest scope: schema field, validator branch, or parser rule.
Confirm by running uv run pytest <targeted> and the existing tests in the same file (no regressions).
Verify error response shape for API paths via tests/contract/test_problem_details.py patterns.

Common pitfalls

Loosening the AST validator to accept user input is a security issue — escalate to rulesgen-security-reviewer.
Pydantic v2 default factories vs default= semantics differ from v1; verify against the v2 docs (use the context7 MCP if needed).
from __future__ import annotations + Pydantic v2 requires explicit model_rebuild() in some forward-reference cases.

同仓库更多 Skills

同仓库

rulesgen-docs-publish

tdspora/tdm_rulesgen

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.

2026-07-020

rulesgen-docs-authoring

tdspora/tdm_rulesgen

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.

2026-05-280

rulesgen-docs-testing

tdspora/tdm_rulesgen

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.

2026-05-280

rulesgen-dsl-authoring

tdspora/tdm_rulesgen

Use for authoring, reviewing, or correcting natural-language → Python generation DSL rules for Rulesgen.

2026-05-280

rulesgen-implement-feature

tdspora/tdm_rulesgen

Use for implementing production-grade Rulesgen features or non-trivial code changes.

2026-05-280

rulesgen-api-debugging

tdspora/tdm_rulesgen

Use for FastAPI route, middleware, lifespan, dependency injection, or Problem Details response issues in Rulesgen.

2026-05-270

Rulesgen Validation Debugging

Workflow

Capture the exact failing input (request body, DSL text, or library call) and the full error message.

Classify the failure:

Pydantic schema — ValidationError raised in rulesgen/schemas/* or rulesgen/domain/models.py. Locate the offending field via the error loc tuple.
DSL parser — failure in rulesgen/compiler/parser.py. Reproduce with a minimal DSL snippet and a unit test in tests/unit/test_compiler.py.
DSL validator — AST rejected by rulesgen/compiler/validator.py. Check whether the rejection is expected for safety; if so, document why; if not, narrow the validator rule.
Runtime properties — type or shape mismatch in RuntimeSpec. Check rulesgen/compiler/runtime_spec.py and tests/unit/test_runtime_properties.py.
API request validation — FastAPI rejected the request before the route. Look at the route signature, the dependency in rulesgen/api/dependencies.py, and the schema in rulesgen/schemas/.

Confirm the contract:

For schema changes: are positive and negative tests present?
For DSL changes: does requirements/NL-to-Python-Generation-DSL.md describe this form?
For API changes: does the error surface as RFC 7807 Problem Details (tests/contract/)?

Write or update a failing test that reproduces the bug before changing production code.

Fix in the smallest scope: schema field, validator branch, or parser rule.

Confirm by running uv run pytest <targeted> and the existing tests in the same file (no regressions).

Verify error response shape for API paths via tests/contract/test_problem_details.py patterns.

Common pitfalls

Loosening the AST validator to accept user input is a security issue — escalate to rulesgen-security-reviewer.

Pydantic v2 default factories vs default= semantics differ from v1; verify against the v2 docs (use the context7 MCP if needed).

from __future__ import annotations + Pydantic v2 requires explicit model_rebuild() in some forward-reference cases.

name	rulesgen-validation-debugging
description	Use for Pydantic v2 validation errors, DSL parser/validator rejections, and API request validation issues in Rulesgen.