validation

You can register shell commands as named validation steps like lint or test, then execute them together as a validation run. This provides a centralized quality gate to verify code quality across projects.

The best way to monitor CI-style checks is to start a validation run that executes registered commands and reports per-command results. You can explore history and track per-command status, durations, and logs to verify code quality.

Yes, this validation tool works across Node.js, Python, and Go projects. It applies conventional name mappings to define and run repeatable CI-style checks like lint and typecheck across different toolchains.

You can manage long-running validation runs by listing active runs and exploring their history. If a run takes too long, you can stop it directly while retaining the per-command status and logs generated up to that point.

You can update or remove existing validation commands using upsert and remove commands. This allows you to manage validation steps dynamically, ensuring your CI-like checks for lint, test, and typecheck remain current as project needs evolve.