Validate Renku blueprints and builds before calling work complete. Use when Codex needs to run blueprint validation, dry-run simulation, produced condition path inspection, costs-only checks, stage-by-stage --up or --up-to-layer validation, root build/test verification, or diagnose validation/runtime errors without invoking paid generation.
Installation
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.
Validate Renku blueprints and builds before calling work complete. Use when Codex needs to run blueprint validation, dry-run simulation, produced condition path inspection, costs-only checks, stage-by-stage --up or --up-to-layer validation, root build/test verification, or diagnose validation/runtime errors without invoking paid generation.
Renku Validate Run
Validate before claiming a blueprint or build is ready. Dry-run evidence is part of the deliverable.
Required Gates
For blueprint changes:
Run blueprint validation through the same surface the user will use.
Run generate --preflight-only with realistic inputs to validate the executable plan without simulation.
Run a dry-run with realistic inputs.
Inspect dry-run validation coverage and produced condition paths when conditions are involved.
Run stage-by-stage checks when the user will use --up or --up-to-layer.
If source code changed, run the repository-required build and tests.
For one-time video inputs:
Validate the blueprint if it changed or if conditions/model configs changed.
Run dry-run with the edited inputs.
Run costs-only when the user is close to paid generation.
Do not run paid generation without explicit approval.
Evidence To Report
Exact command names, not vague statements.
Whether validation had warnings.
Whether preflight passed and which layer scope it checked.
Dry-run job/layer summary.
Condition coverage summary for branch-heavy graphs.
Any residual risks or warnings.
References
Read references/validation-runbook.md before deciding a blueprint/build/source change is complete.
Read references/blueprint-warning-and-error-gotchas.md when validation reports warnings or graph/runtime errors.
Read references/common-errors-advanced-blueprints.md for condition-heavy and model-specific failure patterns.
Read references/validation-checklist.md for command sequence.
Read references/dry-run-feedback.md for interpreting produced condition paths.
Read references/error-codes.md for Renku error-code handling expectations.
