validation

To define repeatable CI-style validation checks, you register shell commands as named validation steps. This allows you to create, update, and upsert checks like lint, tests, and type checks within your project's CI workflows.

The best way to group code quality checks is by composing validation workflows. You combine multiple named checks such as lint, tests, and type checks into a single run to monitor per-command status and results together.

Yes, you can run and monitor validation commands in a minimal shell environment. The system requires only a minimal shell to define, run, stop, and fetch results for checks like lint and typecheck across varying codebase sizes.

To upsert a named validation command for an existing CI workflow, you register or update the shell command. This upsert action ensures your repeatable check is defined without duplicating existing validation entries.

Yes, this validation approach applies to codebases of varying sizes and CI workflows. It enables adding, running, and monitoring named checks like lint, tests, and type checks regardless of project scale.