validation

Registering validation commands as repeatable CI-style checks lets you trigger lint, test, and typecheck commands to verify code quality. You can orchestrate end-to-end validation workflows by starting, stopping, and monitoring runs across development, PRs, and releases.

Managing validation runs requires retrieving detailed per-command and per-run results with logs and summaries. This Skill allows you to list runs, retrieve specific execution details, and stop active checks to maintain control over your code quality workflows.

Yes, validation commands apply across project workflows for software projects and multi-language stacks. You can register checks for different languages and execute them as repeatable CI-style validation steps during your development and release cycles.

You can create and update named validation commands using the upsert functionality. This allows you to define specific validation checks like lint, test, or typecheck, and manage them as repeatable commands within your project workflow.

Yes, the tool supports stopping active runs and retrieving detailed per-command and per-run results. You can access logs and summaries for each validation execution to monitor the outcome of your CI-style checks.