validation

To automate code quality checks, you register custom shell commands as named validation steps for tasks like linting and type-checking. You then execute these commands to automatically run your project's quality suite and track run results including exit codes and error messages.

The best way to run CI-style validation commands is to register them as named steps and trigger their execution. This process monitors the validation runs and provides detailed results, including specific exit codes and error messages for any failed quality checks.

Yes, you can update an existing shell command registered for code validation using the upsert behavior. This allows you to modify and update your registered validation steps for linting, testing, or type-checking without needing to clear previous entries.

You get detailed error messages and exit codes from failed linting or testing runs by executing your registered validation commands. The execution process automatically captures and provides detailed run results, reporting the specific exit code and error output for each step.

No, this validation tool requires no external dependencies to execute type-checking commands. It natively registers and executes the shell commands you define, relying entirely on your existing development environment and project configuration to run the checks.