メニュー
Use when a coding or testing session reveals that a Rulesgen harness file (rule, skill, agent, or doc) is inaccurate, incomplete, or blocking correct work. Requires human approval before any harness file is changed.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | rulesgen-harness-update |
| description | Use when a coding or testing session reveals that a Rulesgen harness file (rule, skill, agent, or doc) is inaccurate, incomplete, or blocking correct work. Requires human approval before any harness file is changed. |
Harness files (.claude/rules/, .claude/skills/, .claude/agents/, .claude/CLAUDE.local.md, root CLAUDE.md) are the operating instructions for all agents working on this project. They must not be changed autonomously — every update requires explicit human approval.
Propose an update when:
python -m pytest while the project uses uv run pytest).CLAUDE.md "project facts" item is stale (version bump, dependency change, new module).docs: Conventional Commit type).rulesgen-test-selection may require an update to testing-contract.md)..claude/settings.json permissions to "make a command work" — escalate the underlying need instead.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.