Register named shell commands and execute them as monitored validation runs.
npx skills add https://github.com/kvm9-dev/susanoo --skill validation-kvm9-dev
Please help me install this Agent Skill. Skill: validation Source: https://github.com/kvm9-dev/susanoo/tree/main/.local/skills/validation Command: npx skills add https://github.com/kvm9-dev/susanoo --skill validation-kvm9-dev
It solves the problem of inconsistently running and tracking project quality checks after changes, so you can quickly know whether linting, tests, or type checks are passing.
Use the validation skill to register your lint and test commands, then start a run for those names to verify the project status after updates.
High-intent search queries and answers about installing and using this skill.
You can register named validation commands for linting and typechecking, then execute them as a single monitored run to verify project quality after updates. The run captures per-command status, exit codes, durations, and log file paths.
Tracking quality check results is done by fetching summaries for a specific run or all runs to monitor project quality over time. This aggregates per-command execution metadata and lifecycle states for historical visibility.
Yes, you can control the run lifecycle by stopping an in-progress validation run. This halts the execution of your registered shell commands and allows you to fetch partial results for the completed checks.
Setting up repeatable CI-style quality checks is done by registering a reusable unit testing command with a stable short name and the shell command to run. You then start a monitored run to execute the registered checks.
Yes, the validation skill operates with no external dependencies or components. It natively automates command orchestration and run monitoring for code quality gates directly during development and CI setup.
The orchestration is limited to executing registered shell commands and capturing their exit codes and durations. It does not perform static code analysis itself, relying entirely on the underlying shell commands you register for validation logic.
akhilksap2026Register shell commands as named validation steps for code quality checks.
epieczkoValidate command manifests and register slash commands in Betty.
26mitch26Merge pull requests, deploy changes, and verify production health via CI/CD pipelines.
InneiCapture and base64-encode task stdout/stderr into an external datastore.
